Interface Criticity
Hi experts,
how would you define :
a high criticity interface ?
a medium ?
a low ?
Kind regards,
Jamal
Adding to what Mike said....
For most of the organization critical interface would be that carries vital information in terms of Business (data).
For an organization handling its customers and suppliers, a customer interface might be more critical than a supplier interface. But saying that its all a definition from the organization itself. They define whats critical to them
Similar Messages
-
PRE won't start / incompatible display driver - AMD HD 6750M
Yesterday I downloaded the trial version of PRE 12, installed it, but it won't run. On startup I get the error message: We have detected an incompatible display driver. To get a better and faster playback performance, please update your display driver. So, I had a look, but both windows and AMD/Samsung say that I have got the latest driver. Re-booted - still no luck. Searched a bit more and somebody suggested to deinstall the AMD Catalyst Manager and re-install. Which I did also, but with no success. Then I deinstalled the driver and/or disabled the card (sorry, I tried so many things to get it to work...), it defaulted back to a generic windows VGA driver. Funnily enough with that one PRE started. I still got the message, but it started. But obviously everything looked ugly and huge. Therefore I reinstalled the latest driver via the Samsung website (since it is a laptop, the drivers are not provided by AMD) and... again, same message, same bad luck = PRE will not start after clicking the message o.k.
Oh, and I did click 'run as admin' and QuickTime is also up to date.
These are the system details:
Samsung Laptop NP700Z5A-S09US series
Windows 7 64bit
AMD Radeon HD6750M
8 GB RAM
Any ideas how to get it to work so I can try it? Thanks a lot!
ClaudiaClaudia,
Several laptop mfgrs. use a dual GPU arrangement, with an embedded Intel chip used to save power, and then an nVidia, or AMD/ATI chip for more intensive computing. Under normal circumstances, the computer will switch between the two, but that is not always the case.
While PrE does not really tax a GPU, like some other programs, it DOES interface critically with the video driver for the GPU. The video driver can be rendered obsolete by such simple things, as an OS update. Most general programs do not need that interfacing with the video driver, and so long as there is a video signal, will function. However, programs like PrE, most extreme games, 3D applications, and CAD programs are different - they need a fully functioning video driver, just to run.
Some users have found that if they disable the Intel GPU (often via the BIOS, or perhaps a jumper/DIP switch on the MoBo), and update the nVidia, or AMD/ATI driver (removing the BadDrivers.TXT file), things work perfectly. Others, whose computers DO switch between the dual GPU's, only require the lastest video drivers for both the Intel and the nVidia, or AMD/ATI chips (with removal of the BadDrivers.TXT file).
I think that it would be better, if the computer mfgrs. had a software toggle switch, that would allow a user to simply turn OFF the power-saving aspect of the Intel chip, when using programs, such as PrE - one would still need to keep that chip's video driver updated, but it would make things easier on people, who wish to edit video, play extreme games, or do any advanced 3D work.
Glad that you found the fix, and that all is working for you.
Happy editing,
Hunt -
Critical physical interface or critical service ?
Hi,
I use a one arm solution ( Trunk interface) in active/standby environment made by 2 CSS 11501, working in router mode. They, each, connect to a separte swicth through the trunk interface. In such configuation, I ask,if configuring critical physical interface is suficient? the switchs are connect through a trunk interface also, and the server and client side are distributed among them in their respectives VLANS.
DavidDavid,
The trunk with the switch could be up but the servers or the default gateway not reachable.
You could add a critical service for the gateway.
Gilles. -
Critical issue regarding file to website interface
hi all,
I am working on one scenario in which sender is an File. and receiver is an HTML page(actually it is a website) which responds according on the input data.
when i visited that site I came to know that there are three fields. as follows...
username:
Password:
File: Browse
POST
Actually file name contains the contents of the file feilds which varies for every transaction.
When i manually put username password and location of the file(using Browse tab) in the website page, I got the response file.
But when I put just file name I am unable to click POST tab.
My problem is:--
Is this thing is possible using XI.
I tried using HTTP and put all three inputs in the header fields of receiver HTTP channel.
But i didn't get the response.
Can anybody tell me any other solution. Since it is critical requirment for me. so Plzz respond ASAP.
Solution will be awarded
Thanks
Jaideep jainHi,
you said that the target system is a website...so can i say that it is a WebService exposed by some XYZ system...if yes then why dont you opt for the receiver SOAP channel....the use of SOAP channel is in such cases only (source: http://help.sap.com/saphelp_nw04/helpdata/en/29/5bd93f130f9215e10000000a155106/frameset.htm )
Also if you have any doubt regarding what kind of adapter to use please refer this discussion: Re: Can't select Adapter Type during creating communication channel.
Adding one more link:
Difference between SOAP and Http Sender
Regarding the target url, u need to use the one which you can see after you hit the Post button.
In the receiver SOAP channel, under the Target URL option u can find the User Authentication details...enter the user details who is authorised to post/upload the document.
Regards,
Abhishek. -
Run SAP PI Interfaces 24X7. How
How I can run PI Interfaces 24X7 to achieve Business Continuity.
The solution provided as u2013
Install Separate additional PI System u2013 called as Federation PI.
Is this solution really applicable?
Details:
1. Our Current Production Landscape holds only One PI System
2. These interfaces hold Critical, Sensitive Finance, employee Data posting to ECC etc.
3. HA options are available and Planned Outages are communicated with Non-SAP Process teams.
4. No performance issues.
5. PI Scaling is in progress to balance load on PI System.
Requirement: We seek PI Production System up and running 24X7 for all above interfaces with out any interruption.
Below Issues: Makes our PI Production System Shut-down for certain period
1. Planned outages
2. Un-planned outages
3. Upgrades
4. Allowed Down-time
5. SPOF
Solution: Federation of SAP PI
1. A very good solution u2013 so that we can switch to another PI System when first PI system is down for any reason.
2. We need to maintain IR, ID objects of interfaces that we planned for 24X7 in both PI Systems.
3. Communication Channels are active in only One PI system.
4. Manual activation of Communication Channels is required when we plan to switch Second PI Server.
That Implies
5. There is minimum amount of downtime is present.
6. So, 24X7 of runtime is not achievable.
My Only one Question:
Is there any automated procedure for this runtime procedure..!!?
Switching in between PI Systems might be possible.
But, how we can implement activation of CC in Second PI System with out manual interaction?Hi,
Currently we are about to start the POC for my client, and the scenarion is like this
We have a ECC system( which will send the IDOC ) and it will be received by my central PI system.( which is is in UK).
The client is present in multiple locations( UK,AUS,US), they want to install the additional PI boxes in AUS and US and they want to have a federation with central PI system which present in UK.
we have two scenarios.
1) The IDOC will trigger from ECC and then it will go to central PI system and then it has to go to local PI system and then to the third party system.
2) The IDOC will trigger from ECC system and then it has to go to the local PI and then to the central PI box and then to the third party system.
Can you please let me know how can achieve these two scenarios and how to install local PI boxes in federation with the central PI box.
Regards,
Pradeep J -
PI 1.3 Interface Monitor is not working
Dear all,
Today, I found one more very basic monitoring of Cisco PI 1.3 is not working.
I enabled interface health monitoring on Cisco PI 1.3 for some critical ports.
However, even I shutdown these ports the PI still show them as UP.
I am really disappointed with PI.
Best Regards1. Yeah I Have checked Changes done on the RPd.
2. I have run a sample report on the answers and also a dashboard created
3. The sample report run has not Dynamic variables or any other system variables.
Thanks for the reply. -
Alert Parameters to Get Interface Description (i.e. Something Meaningful to Network Admins)
Hi All,
We have recently deployed OpsMgr 2012 R2 inparallel to our legacy 2007 environment.
For network device monitoring in the 2007 environment we used the xSNMP Management Pack on top-of the native capabilities.
On of the positive aspects of the 2007 set-up was that we were able to leverage the xSNMP Management Packs ability to expose the interface alias/description which our Network admins populate to identify the connection/purpose of an interface within the SMS
Channel format.
Basically, the Network Admins would give me a list of critical interfaces and using the combination of Path and Alias/Description I would be able to confidently enable interface monitoring and alerting for those interfaces.
In 2012, however, all that has been changed. Now, interfaces are identified by an Interface Name value that is not really meaningful or relevant to the way our Network Admins work. Wjat I also find problematic is the way that interfaces seem
to have been divorced from the the source device in such a way that the default email alert format doesn't even include the Path (source device) on which the interface generating the alert is associated with. This is even the case when trying to create
a custom monitored interfaces State view in that the Path column is populated by the MAC address rather than with the host device that the interface is on which is what really matters. Who deals in MAC addresses?
What we require is a way to expose the host device and Interface Description and Alias values as part of an SMS/email alert as that is crucial information that an on-call engineer being woken-up at 2:00 AM needs to know rather than scratching
their head with some guff about IF-20 without even the parent device of that interface given so that they can at least know what device to log-on to manually try and identify which interface connection/service is down even though they should not have
to do that.
I have already tried to customize the SMS Channel format from its default format to the following:
State: $Data[Default='Not Present']/Context/DataItem/ResolutionStateName$ $Data/Context/DataItem/ManagedEntityFullName$ $Data/Context/DataItem/AlertName$
using the list of alert parameters from Kevin Holman's blog but even with the $Data/Context/DataItem/ManagedEntityFullName parameter the information is not satisfactory.
For all the improvement in SNMP and network monitoring it seems that something that was actually good and useful in 2007 has now been lost because of the way interfaces/ports have been divorced from the parent Managed Network Node device.
Can anyone advise how I might be able to get sensible interface alerts in my email and SMS notifications that provide the host router/switch Display Name, and the Interface Description and Alias of the Interface?
Points given to all considered replies.
Kind Regards,
MichaelYeah, that's kind of a mess...
You can create a workaround to change the name similar like that:
http://www.vroege.biz/?p=746
But it needs some authoring knowledge and must run every time after a network discovery. Since this means a class property change it is a performance consuming workflow and should not run top often.
HTH, Patrick
Please remember to click “Mark as Answer” on the post that helped you.
Patrick Seidl (System Center and Private Cloud)
Website: http://www.syliance.com
Blog: http://www.systemcenterrocks.com -
WARNING! Server MOM has experienced a critical error.
Good Afternoon,
I work for a non-profit with a single Novell server that is mainly used for Faxpress and File Shares. Today before I was about to leave I was hit with
WARNING! Server MOM has experienced a critical error. It is going down in 2 minutes. Save your files and logout.
I went and got the error logs and the apend log showing the errors that took place. I am only copying and pasting the errors I received today. Not a history of errors.
First up Error Log
10-25-2011 10:51:29 am: SERVER-5.70-4
Severity = 4 Locus = 18 Class = 6
WARNING! Server MOM has experienced a critical error. It is going down in 2 minutes. Save your files and logout.
10-25-2011 11:11:21 am: NCP-5.60-66
Severity = 0 Locus = 14 Class = 19
The Network Address [TCP 192.168.10.47:0524] has been registered as an NCP Service Address.
10-25-2011 11:11:21 am: NCP-5.60-66
Severity = 0 Locus = 14 Class = 19
The Network Address [UDP 192.168.10.47:0524] has been registered as an NCP Service Address.
10-25-2011 11:11:21 am: NCP-5.60-66
Severity = 0 Locus = 14 Class = 19
The Network Address [TCP 192.168.10.46:0524] has been registered as an NCP Service Address.
10-25-2011 11:11:21 am: NCP-5.60-66
Severity = 0 Locus = 14 Class = 19
The Network Address [UDP 192.168.10.46:0524] has been registered as an NCP Service Address.
10-25-2011 11:11:23 am: DS-10551.13-264
Severity = 1 Locus = 17 Class = 19
Bindery open requested by the SERVER
10-25-2011 11:11:23 am: CE1000-7.34-0
Severity = 0 Locus = 4 Class = 5 ID = 0x1070000
CE1000-NW-000-Adapter 1-Board 1:
Link is up. 100 Mbs Full Duplex
10-25-2011 11:11:23 am: CE1000-7.34-0
Severity = 0 Locus = 4 Class = 5 ID = 0x1070000
CE1000-NW-000-Adapter 2-Board 5:
Link is up. 100 Mbs Full Duplex
10-25-2011 11:11:25 am: NCP-5.60-66
Severity = 0 Locus = 14 Class = 19
The Network Address [IPX 38DE5076:000001:451] has been registered as an NCP Service Address.
10-25-2011 11:11:41 am: AFPTCP-2.1-259
Severity = 1 Locus = 17 Class = 0
Desktop on volume _ADMIN is unavailable to AFP clients.
10-25-2011 11:11:55 am: DS-10551.13-262
Severity = 1 Locus = 17 Class = 19
Directory Services: Local database is open
10-25-2011 11:45:30 am: SERVER-5.70-4
Severity = 4 Locus = 18 Class = 6
WARNING! Server MOM has experienced a critical error. It is going down in 2 minutes. Save your files and logout.
10-25-2011 12:05:55 pm: NCP-5.60-66
Severity = 0 Locus = 14 Class = 19
The Network Address [TCP 192.168.10.47:0524] has been registered as an NCP Service Address.
10-25-2011 12:05:55 pm: NCP-5.60-66
Severity = 0 Locus = 14 Class = 19
The Network Address [UDP 192.168.10.47:0524] has been registered as an NCP Service Address.
10-25-2011 12:05:55 pm: NCP-5.60-66
Severity = 0 Locus = 14 Class = 19
The Network Address [TCP 192.168.10.46:0524] has been registered as an NCP Service Address.
10-25-2011 12:05:55 pm: NCP-5.60-66
Severity = 0 Locus = 14 Class = 19
The Network Address [UDP 192.168.10.46:0524] has been registered as an NCP Service Address.
10-25-2011 12:05:56 pm: DS-10551.13-264
Severity = 1 Locus = 17 Class = 19
Bindery open requested by the SERVER
10-25-2011 12:05:57 pm: CE1000-7.34-0
Severity = 0 Locus = 4 Class = 5 ID = 0x1070000
CE1000-NW-000-Adapter 1-Board 1:
Link is up. 100 Mbs Full Duplex
10-25-2011 12:05:57 pm: CE1000-7.34-0
Severity = 0 Locus = 4 Class = 5 ID = 0x1070000
CE1000-NW-000-Adapter 2-Board 5:
Link is up. 100 Mbs Full Duplex
10-25-2011 12:06:00 pm: NCP-5.60-66
Severity = 0 Locus = 14 Class = 19
The Network Address [IPX 38DE5076:000001:451] has been registered as an NCP Service Address.
10-25-2011 12:06:16 pm: AFPTCP-2.1-259
Severity = 1 Locus = 17 Class = 0
Desktop on volume _ADMIN is unavailable to AFP clients.
10-25-2011 12:06:29 pm: DS-10551.13-262
Severity = 1 Locus = 17 Class = 19
Directory Services: Local database is open
Next up Apend Log with the 2 instances.
Tuesday, October 25, 2011 10:51:28.877 am
Abend 1 on P00: Server-5.70.02-0: NCPIP: ReplyDisgard overflowed reply buffer!!
Registers:
CS = 0060 DS = 007B ES = 007B FS = 007B GS = 007B SS = 0068
EAX = 00000002 EBX = 000005F0 ECX = 000005E8 EDX = 863BC980
ESI = 000005F0 EDI = 00000001 EBP = 00000008 ESP = 186BDF4C
EIP = 85026318 FLAGS = 00000216
85026318 83C404 ADD ESP, 00000004
EIP in NCPIP.NLM at code start +00003318h
The violation occurred while processing the following instruction:
85026318 83C404 ADD ESP, 00000004
8502631B 8B44240C MOV EAX, [ESP+0C]
8502631F 6AFE PUSH FE
85026321 83C00C ADD EAX, 0000000C
85026324 50 PUSH EAX
85026325 E826250E7B CALL SERVER.NLM|atomic_and
8502632A 83C408 ADD ESP, 00000008
8502632D 8B44240C MOV EAX, [ESP+0C]
85026331 F6400D TEST byte ptr [EAX+0D]
85026334 0174518B ADD [ECX+EDX*2-75], ESI
Running process: Server 00:87 Process
Thread Owned by NLM: SERVER.NLM
Stack pointer: 186BDA98
OS Stack limit: 186B7020
Scheduling priority: 67371008
Wait state: 5050090 Wait for interrupt
Stack: -8503BBDC (NCPIP.NLM|(Data Start)+BDC)
--863BCA0E ?
--863BCA0E ?
--863BCA5C ?
--863BC980 ?
--186BEF00 ?
--863BCA5C ?
--863BCA34 ?
--863BD044 ?
80162219 (NWSA.NSS|NSSCase89+459)
--863BCA34 ?
--00000000 ?
--00000001 ?
--863BCA5C ?
--000005E8 ?
B7C834EF (NSS.NLM|NSSMPK_UnlockNss+1F)
-B7F18C68 (NSS.NLM|NSSMPK_spinlock+0)
--00000000 ?
--186BE054 ?
8026BAE5 (COMN.NSS|zGetInfo+A5)
--00000000 ?
--186BE0B4 ?
--00000000 ?
--00000000 ?
--5060C960 ?
--3DEABEC0 ?
--00000001 ?
--186BE798 ?
--000004BC ?
--00000000 ?
--00000001 ?
--186BE0B4 ?
--00000000 ?
--00000000 ?
--00000050 ?
--00000000 ?
--00000001 ?
--00000000 ?
--B00771A0 ?
--00000001 ?
--186BE0B4 ?
--00000001 ?
--00000000 ?
--186BE028 ?
B633BB16 (LIBC.NLM|VerifyPathInfo+216)
--00000001 ?
--FFFFFFFF (LOADER.NLM|KernelTempAliasesEnd+FFF)
--186BE0B4 ?
--186BE750 ?
--186BE080 ?
--186BE54A ?
--00000000 ?
-82E11BC8 (WS2_32.NLM|ProtocolPath+0)
--B007B700 ?
-82E11BC8 (WS2_32.NLM|ProtocolPath+0)
--186BE054 ?
--B007B700 ?
--87A36585 ?
--B0075AC0 ?
B633C721 (LIBC.NLM|BuildUnicodePath+161)
--FFFFFFFF (LOADER.NLM|KernelTempAliasesEnd+FFF)
--B0075AD2 ?
--87A36585 ?
--00000001 ?
--00000000 ?
--186BE768 ?
--186BEC70 ?
B634DFA7 (LIBC.NLM|kgFileOpenEx+517)
--E31625E9 ?
--186BEC70 ?
--00000001 ?
--00000000 ?
--E2C7444E ?
B634E89C (LIBC.NLM|kgFileOpenEx+E0C)
--B0075AC0 ?
--87A362C0 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
-00535953 (SERVER.NLM|RDebugPollTimeoutTimer+E11F)
--00000000 ?
--00000000 ?
--00000000 ?
--5C435445 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
Additional Information:
The NetWare OS detected a problem with the system while executing a process owned by NCPIP.NLM. It may be the source of the problem or there may have been a memory corruption.
Loaded Modules:
MONITOR.NLM NetWare Console Monitor
Version 12.01.09 May 5, 2004
Code Address: 21288000h Length: 00022AAFh
Data Address: 20FC6000h Length: 00005ED1h
NWSNUT.NLM NetWare NLM Utility User Interface
Version 7.00 June 22, 2004
Code Address: 21274000h Length: 00013417h
Data Address: 0F4FA000h Length: 000006F8h
CPWDPLSM.NLM Change Password PLSM
Version 1.02 March 31, 2004
Code Address: 92372000h Length: 0000DEBBh
Data Address: 92381000h Length: 000013D0h
LCMCIFS2.NLM Windows Native File Access Login Methods (Build 70 SP)
Version 2.00.05 May 10, 2004
Code Address: 92314000h Length: 0000E011h
Data Address: 92324000h Length: 000016B0h
LSMCIFS2.NLM Windows Native File Access Login Methods (Build 81 SP)
Version 2.00.07 May 10, 2004
Code Address: 922BE000h Length: 0000F011h
Data Address: 922CF000h Length: 000017B0h
LSMAFP3.NLM Macintosh Native File Access Login Methods (Build 103 SP)
Version 2.00.11 May 10, 2004
Code Address: 9224D000h Length: 0000F24Eh
Data Address: 9225E000h Length: 000013C0h
SASL.NLM Simple Authentication and Security Layer
Version 1.02 June 17, 2004
Code Address: 8DDB0000h Length: 0000053Eh
Data Address: 8DDB2000h Length: 00000034h
NMASLDAP.NLM NMAS LDAP Extension
Version 1.20 March 31, 2004
Code Address: 8D7A3000h Length: 00001F93h
Data Address: 8D7A6000h Length: 000005D0h
LDAPXS.NLM (Clib version)
Version 3.01 November 13, 2003
Code Address: 8D79C000h Length: 00003B05h
Data Address: 8D7A1000h Length: 00000770h
LBURP.NLM LDAP Bulkload Update/Replication Protocol service extension for Novell eDirectory 8.7.
Version 10552.36 December 2, 2003
Code Address: 8D786000h Length: 000010ECh
Data Address: 8D789000h Length: 00000444h
VOLSMS.NLM NSS Distributed Volume Manager (Build 207 MP)
Version 3.22 May 14, 2004
Code Address: 8DCF8000h Length: 00017211h
Data Address: 8DCE8000h Length: 00001770h
VMRPC.NLM DFS Volume Manager RPC interface (Build 349 MP)
Version 3.22 May 14, 2004
Code Address: 8DCEF000h Length: 00003623h
Data Address: 8DCF4000h Length: 000002FDh
NLSTRAP.NLM NetWare License Server Trap
Version 5.02 February 19, 2004
Code Address: 8DC03000h Length: 0000298Ah
Data Address: 8DC07000h Length: 00000695h
NDMPD.NLM Backup Exec NDMP Server Module
Version 9.20 November 29, 2006
Code Address: 8D937000h Length: 0005E633h
Data Address: 8D8D8000h Length: 000192F0h
AD_ASPI.NLM Backup Exec ASPI Device Driver for NetWare
Version 7.50 September 25, 2006
Code Address: 8D916000h Length: 000141B8h
Data Address: 8D92C000h Length: 0000910Fh
NRLTLI.NLM Backup Exec - Remote Workstation Backup Software
Version 9.20 November 29, 2006
Code Address: 8D6E8000h Length: 0000240Fh
Data Address: 8D6EC000h Length: 00000BE0h
TSANDS.NLM TSA for Novell eDirectory 7.x, 8.x
Version 10551.61 December 2, 2003
Code Address: 8D7B5000h Length: 0001254Ch
Data Address: 8D6FC000h Length: 00001410h
JNET.NLM Java jnet (based on 1.4.2_04)
Version 1.42.03 June 15, 2004
Code Address: 8D70A000h Length: 0000640Eh
Data Address: 8D712000h Length: 00001110h
DBNET6.NLM Debug Network IO Support
Version 1.43.07 December 2, 2003
Code Address: 8D3F8000h Length: 0001B5C8h
Data Address: 8D39F000h Length: 000124B8h
IPMCFG.NLM Web Interface for IP Address Management
Version 1.01.14 October 14, 2003
Code Address: 8D230000h Length: 0000A479h
Data Address: 8D23C000h Length: 0000B610h
NIRMAN.NLM TCPIP - NetWare Internetworking Remote Manager
Version 1.04.02 January 27, 2004
Code Address: 8D2E0000h Length: 0005F160h
Data Address: 8D341000h Length: 00018E0Ah
TCPSTATS.NLM Web Interface for Protocol Monitoring
Version 6.50.10 June 20, 2003
Code Address: 8D1C8000h Length: 0000E5ECh
Data Address: 8D1D8000h Length: 00005460h
NLSADPT2.NLM NLS and Metering adapter for iManager 2.0 plugin
Version 2.00 September 9, 2003
Code Address: 8D0CD000h Length: 0000665Dh
Data Address: 8D0D5000h Length: 00000E7Dh
NLSLRUP.NLM NLS - Usage Metering
Version 4.01.06 March 16, 2004
Code Address: 8D128000h Length: 0003BA0Ah
Data Address: 8D165000h Length: 00010AE0h
HWDETECT.NLM Novell Hardware Insertion/Removal Detection
Version 1.19.05 February 20, 2003
Code Address: 8CFEF000h Length: 00002B33h
Data Address: 8CFF3000h Length: 00000D3Ch
BKUPEXEC.NLM Backup Exec SureStart
Version 9.20 November 29, 2006
Code Address: 8D033000h Length: 0001D57Ch
Data Address: 8D052000h Length: 00013040h
RSYNCNRM.NLM Novell(R) Nterprise(TM) Branch Office(TM) RSYNC NRM interface
Version 2.00 March 30, 2004
Code Address: 8CD90000h Length: 0000821Ch
Data Address: 8CD9A000h Length: 00003ED0h
XNFS.NLM NetWare NFS - NFS Server for NetWare 6.5
Version 1.01.11 May 10, 2004
Code Address: 8CA45000h Length: 0001D6F2h
Data Address: 8C8E2000h Length: 0000515Ch
BTCPCOM.NLM BTCPCOM.NLM v7.90.000, Build 253
Version 7.90 July 9, 2003
Code Address: 8C8D2000h Length: 00004450h
Data Address: 8C8D8000h Length: 00000CECh
NISSWDD.NLM NetWare NFS - NIS Password Management Support Module
Version 15.00.25 November 5, 2003
Code Address: 8CA82000h Length: 00002E49h
Data Address: 8CA86000h Length: 00002390h
NDSILIB.NLM NetWare NFS - eDirectory Interface Library
Version 15.02.24 June 15, 2004
Code Address: 8CAE3000h Length: 0000D62Eh
Data Address: 8CAF2000h Length: 0000BD50h
NISBIND.NLM NetWare NFS - NIS Client Module
Version 15.01.06 November 5, 2003
Code Address: 8CA9A000h Length: 00007E69h
Data Address: 8CA69000h Length: 00003870h
UNICRYPT.NLM TCP/IP Encryption NLM
Version 9.11 December 15, 1998
Code Address: 8BDA8000h Length: 000004D9h
Data Address: 8BDAA000h Length: 000007C8h
NFSADMIN.NLM NetWare NFS - ConsoleOne Administration Support Module
Version 15.01.02 October 27, 2003
Code Address: 8C6F9000h Length: 00003ED1h
Data Address: 8C6FE000h Length: 000008E0h
PKERNEL.NLM NetWare NFS - Portmapper and RPC Module
Version 15.01.19 May 10, 2004
Code Address: 8C9A5000h Length: 00016E57h
Data Address: 8C9BE000h Length: 0000F700h
RPCBSTUB.NLM NetWare NFS - Portmapper & Rpcbind co-existance Support Module
Version 15.00.14 November 17, 2003
Code Address: 8C8CE000h Length: 00000041h
Data Address: 8C8D0000h Length: 00000008h
TSAFS.NLM SMS - File System Agent for NetWare 6.X
Version 6.50.09 June 7, 2004
Code Address: 8C4F3000h Length: 000557C2h
Data Address: 8C54A000h Length: 0000C450h
SPXS.MPM spxs Memory Protection Module
Version 5.70 April 1, 2004
Code Address: 8C4EF000h Length: 0000002Ah
Data Address: 8C4F1000h Length: 00000018h
SPXS.NLM NetWare SPX/SPXII Protocol (PTF)
Version 5.14 January 18, 2000
Code Address: 8C274000h Length: 0000A021h
Data Address: 8C280000h Length: 00000FD8h
Global Code Address: 8C282000h Length: 00001000h
SMDR.NLM SMS - Storage Data Requestor
Version 6.54.01 June 11, 2004
Code Address: 8C15E000h Length: 0002F3F7h
Data Address: 8C18F000h Length: 0000456Ch
BSPXCOM.NLM BSPXCOM.NLM v7.90.000, Build 253
Version 7.90 April 15, 2003
Code Address: 8BF52000h Length: 0000530Ah
Data Address: 8BF59000h Length: 00000BB0h
NDSIMON.NLM NDS iMonitor 2.3
Version 20210.61 June 2, 2004
Code Address: 8C2C7000h Length: 0010BF39h
Data Address: 8B9A7000h Length: 0008A640h
NWBSRVCM.NLM NWBSRVCM.NLM v7.90.000, Build 230
Version 7.90 March 20, 2001
Code Address: 8BD5A000h Length: 00006776h
Data Address: 8BD62000h Length: 00000AD0h
MONDATA.NLM NetWare 5.x/6.x Monitor MIB
Version 6.00 July 18, 2003
Code Address: 8BD3A000h Length: 00008C9Fh
Data Address: 8BD44000h Length: 00004DD1h
SERVINST.NLM NetWare 5.x/6.x Instrumentation
Version 5.00.10 September 26, 2003
Code Address: 8BBDA000h Length: 00010C0Ch
Data Address: 8BC99000h Length: 000074D4h
NWTRAP.NLM NetWare 5.x/6.x Trap Monitor
Version 6.00.01 October 10, 2003
Code Address: 8BA49000h Length: 000065F3h
Data Address: 8BB0E000h Length: 0000A2D0h
HOSTMIB.NLM NetWare 5.x/6.x Host Resources MIB
Version 5.00.13 April 27, 2004
Code Address: 8BA53000h Length: 0000B560h
Data Address: 8BA8E000h Length: 00003CE8h
SERVICTL.NLM eDirectory Management Tool Box DSService eMTool
Version 10553.18 June 7, 2004
Code Address: 8B859000h Length: 0000B932h
Data Address: 8B866000h Length: 00004210h
LSL.MPM lsl Memory Protection Module
Version 5.70 April 1, 2004
Code Address: 8B758000h Length: 000001C2h
Data Address: 8B851000h Length: 00000138h
SCHEMACR.NLM eDirectory Management Tool Box Schema eMTool
Version 10553.18 June 7, 2004
Code Address: 8B7EB000h Length: 00012861h
Data Address: 8B7FF000h Length: 0000FF1Ch
SLP.MPM slp Memory Protection Module
Version 5.70 March 26, 2003
Code Address: 8B754000h Length: 000002E9h
Data Address: 8B756000h Length: 00000090h
STREAMS.MPM streams Memory Protection Module
Version 5.70 April 1, 2004
Code Address: 8B748000h Length: 000006E9h
Data Address: 8B74A000h Length: 00000188h
IPXSPX.MPM ipxspx Memory Protection Module
Version 5.70 April 1, 2004
Code Address: 8B75E000h Length: 00000C33h
Data Address: 8B760000h Length: 000004B8h
SCHEMATL.NLM eDirectory Management Tool Box Schema eMTool
Version 10553.18 June 7, 2004
Code Address: 8B768000h Length: 00009CB2h
Data Address: 8B773000h Length: 00005EDCh
TLI.MPM tli Memory Protection Module
Version 5.70 April 1, 2004
Code Address: 8A5B1000h Length: 00001276h
Data Address: 8A5B4000h Length: 00000344h
REPAIRCR.NLM eDirectory Management Tool Box DSRepair eMTool
Version 10553.18 June 7, 2004
Code Address: 8A78A000h Length: 0003D871h
Data Address: 8B70D000h Length: 0001F980h
SNMP.MPM snmp Memory Protection Module
Version 5.70 April 1, 2004
Code Address: 8A63D000h Length: 000009F7h
Data Address: 8A63F000h Length: 000000FCh
IPXS.MPM ipxs Memory Protection Module
Version 5.70 April 1, 2004
Code Address: 8A511000h Length: 0000002Ah
Data Address: 8A513000h Length: 00000018h
REPAIRTL.NLM eDirectory Management Tool Box DSRepair eMTool
Version 10553.18 June 7, 2004
Code Address: 8A4E0000h Length: 00010562h
Data Address: 8A4F2000h Length: 0001DCBCh
TCPIP.MPM tcpip Memory Protection Module
Version 5.70 April 1, 2004
Code Address: 8A3ED000h Length: 00001EC3h
Data Address: 8A3B3000h Length: 00000918h
NETDB.MPM netdb Memory Protection Module
Version 5.70 April 1, 2004
Code Address: 8A38D000h Length: 00000AC5h
Data Address: 8A38F000h Length: 000001C4h
MERGECR.NLM eDirectory Management Tool Box DSMerge eMTool
Version 10553.18 June 7, 2004
Code Address: 8A705000h Length: 0001B231h
Data Address: 8A722000h Length: 00016BF4h
SYSCALLS.NLM NetWare Operating System Call and Marshalling Library
Version 5.60 April 29, 2004
Code Address: 8A347000h Length: 0000ED18h
Data Address: 8A357000h Length: 0000AEECh
MERGETL.NLM eDirectory Management Tool Box DSMerge eMTool
Version 10553.18 June 7, 2004
Code Address: 8A29C000h Length: 0000B812h
Data Address: 8A2A9000h Length: 0000F88Dh
PMPORTAL.NLM NetWare License Information Portal
Version 2.16 November 21, 2003
Code Address: 8A210000h Length: 000071C9h
Data Address: 8A219000h Length: 00004360h
LANGMANI.NLM Novell Cross-Platform Language Manager
Version 10210.40 November 10, 2003
Code Address: 8A1E8000h Length: 000040F2h
Data Address: 8A05F000h Length: 00001084h
APRLIB.NLM Apache Portability Runtime Library 0.9.5
Version 0.09.05 March 29, 2004
Code Address: 8A0D1000h Length: 0002E098h
Data Address: 8A101000h Length: 00008160h
BACKUPCR.NLM eDirectory Management Tool Box DSBackup eMTool
Version 10553.18 June 7, 2004
Code Address: 89D88000h Length: 00009F21h
Data Address: 8878B000h Length: 00002E48h
BACKUPTL.NLM eDirectory Management Tool Box DSBackup eMTool
Version 10553.18 June 7, 2004
Code Address: 89DA2000h Length: 0000AF72h
Data Address: 89DAE000h Length: 000052C8h
NCPL.NLM Novell XTier Base Services
Version 2.06 June 7, 2004
Code Address: 89D78000h Length: 0000B48Ch
Data Address: 89D85000h Length: 00001170h
MYSQLD.NLM MySQL Database Server
Version 4.00.18 May 25, 2004
Code Address: 88D47000h Length: 001685ADh
Data Address: 88EB1000h Length: 000B6F01h
LOGGER.NLM eDirectory Management Tool Box Logger
Version 10553.18 June 7, 2004
Code Address: 88BA0000h Length: 0000DF82h
Data Address: 88BAF000h Length: 0000664Ch
STATUSLG.NLM Report and Notification Service
Version 1.00 August 8, 2003
Code Address: 88CED000h Length: 00058A5Eh
Data Address: 88AF0000h Length: 000187E0h
LLDAPSSL.NLM NetWare SSL Library for LDAP SDK (LibC version)
Version 3.01 November 13, 2003
Code Address: 88B3F000h Length: 0005F156h
Data Address: 88A33000h Length: 0001882Dh
EMSECURE.NLM eDirectory Management Tool Box Security Service
Version 10553.18 June 7, 2004
Code Address: 889F0000h Length: 00009852h
Data Address: 889FB000h Length: 000033B0h
LLDAPX.NLM NetWare Extension APIs for LDAP SDK (LibC version)
Version 3.01 November 13, 2003
Code Address: 889E9000h Length: 000057C5h
Data Address: 88611000h Length: 00000DC0h
RSS.NLM eDirectory Management Tool Box Remote Subscription Service
Version 10553.18 June 7, 2004
Code Address: 885FA000h Length: 00009932h
Data Address: 88605000h Length: 0000261Ch
ISCSILIB.NLM NetWare iSCSI Library
Version 1.02 June 4, 2004
Code Address: 8868F000h Length: 0001AAABh
Data Address: 886AB000h Length: 00005D60h
EMBOXMGR.NLM eDirectory Management Tool Box Manager
Version 10553.18 June 7, 2004
Code Address: 8866D000h Length: 00018D92h
Data Address: 8898E000h Length: 0000790Ah
EMBOXMSG.NLM eDirectory Management Tool Box Message API
Version 10553.18 June 7, 2004
Code Address: 88659000h Length: 0000B2F2h
Data Address: 885D3000h Length: 0000273Dh
IOCTL.NLM NetWare IoCtl Library
Version 1.02 June 4, 2004
Code Address: 885EB000h Length: 00001181h
Data Address: 88637000h Length: 00002400h
HT2SOAP.NLM eDirectory Management Tool Box HTTP to SOAP shim
Version 10553.18 June 7, 2004
Code Address: 88614000h Length: 00009B02h
Data Address: 885C1000h Length: 00003408h
DLOG.NLM Debug Memory Log Functions
Version 6.05 November 18, 2003
Code Address: 885C9000h Length: 00001FCDh
Data Address: 885CC000h Length: 00003BB8h
MYSQLD_SAFE. MySQL Database Server Monitor
Version 4.00.18 May 25, 2004
Code Address: 884EA000h Length: 000012CDh
Data Address: 884ED000h Length: 00002264h
LANGMAN.NLM Novell Cross-Platform Language Manager
Version 10210.40 November 10, 2003
Code Address: 88541000h Length: 0000E6A0h
Data Address: 885AE000h Length: 0000B4A1h
XI18N.NLM Novell Cross-Platform Internationalization Package
Version 10210.40 November 10, 2003
Code Address: 8855A000h Length: 0001CA12h
Data Address: 88578000h Length: 00007EC8h
EMBOX.NLM eDirectory Management Tool Box Engine
Version 10553.18 June 7, 2004
Code Address: 880E6000h Length: 00007B02h
Data Address: 880EF000h Length: 00004F20h
XIS11.NLM XML Integration Service
Version 1.00.01 November 7, 2003
Code Address: 881CE000h Length: 0009937Ch
Data Address: 87F0D000h Length: 0004400Eh
NLDAP.NLM LDAP Agent for Novell eDirectory 8.7.3
Version 10552.88 May 21, 2004
Code Address: 87F9E000h Length: 000739B8h
Data Address: 88013000h Length: 00044AB4h
CIFSPROX.NLM NMAS Proxy for CIFS (Build 130 MP)
Version 3.22 May 24, 2004
Code Address: 8787A000h Length: 0001300Eh
Data Address: 878AA000h Length: 00005940h
LDAPX.NLM NetWare Extension APIs for LDAP SDK (Clib version)
Version 3.01 November 13, 2003
Code Address: 87857000h Length: 000057D5h
Data Address: 8785E000h Length: 00000DC0h
CIFS.NLM CIFS Semantic Agent (Build 451 MP)
Version 3.22 June 11, 2004
Code Address: 87AB0000h Length: 00061751h
Data Address: 879AE000h Length: 00011320h
VLRPC.NLM DFS Volume Location Database (VLDB) RPC interface (Build 480 MP)
Version 3.22 May 14, 2004
Code Address: 87994000h Length: 00002FB3h
Data Address: 87999000h Length: 000002FDh
JSTCP.NLM Jetstream TCP Transport Layer (Build 537 MP)
Version 3.22 May 14, 2004
Code Address: 87933000h Length: 00004E90h
Data Address: 87939000h Length: 000001E0h
JSMSG.NLM Jetstream Message Layer (Build 557 MP)
Version 3.22 May 14, 2004
Code Address: 87940000h Length: 00006370h
Data Address: 87948000h Length: 00000220h
DFSLIB.NLM DFS Common Library (Build 450 MP)
Version 3.22 May 14, 2004
Code Address: 8789A000h Length: 000005C3h
Data Address: 8789C000h Length: 00000080h
AFPTCP.NLM AFPTCP (Build 288 SP)
Version 2.01.13 May 14, 2004
Code Address: 8776C000h Length: 0002D35Dh
Data Address: 87404000h Length: 00009DF0h
WSPDSI.NLM NetWare Winsock Service 1.0 NLM for Data Stream Interface
Version 6.21 March 22, 2004
Code Address: 873FE000h Length: 00002E80h
Data Address: 87402000h Length: 000006D4h
NFAP4NRM.NLM NFAP Simple Password Management NLM
Version 1.04 December 8, 2003
Code Address: 876E4000h Length: 000080A2h
Data Address: 87704000h Length: 00017CA0h
PORTAL.NLM NetWare Remote Manager NLM
Version 3.00 June 11, 2004
Code Address: 87598000h Length: 000E2889h
Data Address: 874C4000h Length: 00060E90h
NWIDK.NLM CDWare Volume Module
Version 3.01.01 September 19, 2003
Code Address: 874BC000h Length: 00004640h
Data Address: 874C2000h Length: 00000730h
SETMD4.NLM Windows Native File Access CIFS Library (Build 91 SP)
Version 2.00.01 May 10, 2004
Code Address: 87464000h Length: 0000125Ch
Data Address: 87467000h Length: 00000130h
NMASGPXY.NLM NMAS Generic Proxy
Version 1.04 June 17, 2004
Code Address: 873D4000h Length: 00000BC8h
Data Address: 873D6000h Length: 00000098h
ACPISBD.NLM System Bus Driver for ACPI compliant systems
Version 1.04 June 1, 2004
Code Address: 86D08000h Length: 00002590h
Data Address: 86D0C000h Length: 00000461h
NCM.NLM Novell Configuration Manager
Version 1.14.03 March 27, 2003
Code Address: 86D11000h Length: 0000484Ch
Data Address: 86D17000h Length: 00000F00h
WSPSSL.NLM NetWare Winsock Service 1.0 NLM for SSL
Version 6.21 March 22, 2004
Code Address: 872BA000h Length: 000062CBh
Data Address: 872C2000h Length: 000108BFh
HTTPSTK.NLM Novell Small Http Interface
Version 3.00 April 20, 2004
Code Address: 86EFB000h Length: 000206C7h
Data Address: 86F1D000h Length: 000179C8h
NILE.NLM Novell Secure Socket Services NLM
Version 6.04.02 November 21, 2003
Code Address: 871C6000h Length: 0005467Bh
Data Address: 8704C000h Length: 0001F620h
NPKIAPI.NLM Public Key Infrastructure Services
Version 2.73 May 19, 2004
Code Address: 86E75000h Length: 0002D797h
Data Address: 87018000h Length: 0001751Fh
NPKIT.NLM Public Key Infrastructure Services
Version 2.73 June 1, 2004
Code Address: 86F3B000h Length: 000268D0h
Data Address: 86F63000h Length: 00013E93h
NTLS.NLM Novell TLS Library
Version 10810.04 March 25, 2004
Code Address: 8714E000h Length: 00076F16h
Data Address: 86F78000h Length: 0002DEE7h
LLDAPSDK.NLM LDAP SDK Library (LibC version)
Version 3.01 November 13, 2003
Code Address: 86A52000h Length: 0001CEBBh
Data Address: 86A70000h Length: 0000611Ch
PKI.NLM Novell Certificate Server
Version 2.73 May 19, 2004
Code Address: 86DB1000h Length: 00084305h
Data Address: 86D34000h Length: 0003E860h
PKIAPI.NLM Public Key Infrastructure Services
Version 2.23.08 April 1, 2004
Code Address: 86D78000h Length: 00037141h
Data Address: 8653A000h Length: 00006454h
LDAPSDK.NLM LDAP SDK Library (Clib version)
Version 3.01 November 13, 2003
Code Address: 86679000h Length: 0001CE0Bh
Data Address: 86530000h Length: 000066D9h
NWUTIL.NLM Novell Utility Library NLM ()
Version 1.03.05 November 21, 2003
Code Address: 8647D000h Length: 000128D8h
Data Address: 86491000h Length: 00019D14h
CWD.NLM Perl 5.8.0 - Cwd Extension XS_VERSION: 2.06
Version 3.20.02 January 14, 2004
Code Address: 865D6000h Length: 000011FAh
Data Address: 865D9000h Length: 0000066Ch
ZIP.NLM Java zip (based on 1.4.2_04)
Version 1.42.03 June 15, 2004
Code Address: 86352000h Length: 0000AD8Ch
Data Address: 8635E000h Length: 00001B90h
JVMLIB.NLM Java jvmlib (based on 1.4.2_04)
Version 1.42.03 June 15, 2004
Code Address: 86371000h Length: 000170D4h
Data Address: 8638A000h Length: 00008670h
VERIFY.NLM Java verify (based on 1.4.2_04)
Version 1.42.03 June 15, 2004
Code Address: 862F1000h Length: 00008774h
Data Address: 862FB000h Length: 00001BC0h
JVM.NLM Java Hotspot 1.4.2_04 Interpreter
Version 1.42.03 June 15, 2004
Code Address: 866BE000h Length: 00214CCFh
Data Address: 868D4000h Length: 00060590h
IPMGMT.NLM TCPIP - NetWare IP Address Management
Version 1.02.01 February 25, 2004
Code Address: 861A0000h Length: 0002B97Dh
Data Address: 861CD000h Length: 00005BF8h
JSOCK6X.NLM NetWare 6.x Support For Java Sockets (JDK 1.4.2)
Version 1.42.03 June 15, 2004
Code Address: 85E11000h Length: 0000DCD8h
Data Address: 85E20000h Length: 000027E4h
JAVA.NLM java.nlm (based on 1.4.2_04) Build 04061513
Version 1.42.03 June 15, 2004
Code Address: 85E86000h Length: 00033925h
Data Address: 85EBB000h Length: 0000C508h
JSOCK.NLM Support For Java Sockets (loader)
Version 1.42.03 June 15, 2004
Code Address: 85E71000h Length: 00000086h
Data Address: 85E73000h Length: 00000064h
PERL.NLM Perl 5.8.0 - Script interpreter for NetWare
Version 3.20.02 March 19, 2004
Code Address: 86006000h Length: 000F0408h
Data Address: 860F8000h Length: 0001FF3Ch
NWSEC.NLM Scripting - Security Library
Version 1.00.02 January 13, 2004
Code Address: 85FB7000h Length: 00003B69h
Data Address: 85FBC000h Length: 00000ADCh
NETDB.NLM Network Database Access Module
Version 4.10.26 June 27, 2003
Code Address: 85F3A000h Length: 00013933h
Data Address: 85F4F000h Length: 000025FCh
ODINEB.NLM Novell ODI to Novell Event Bus Interface Module
Version 1.10 August 13, 1999
Code Address: 85CD0000h Length: 000012E9h
Data Address: 85CD3000h Length: 0000077Ch
SPMDCLNT.NLM Novell SPM Client for DClient
Version 1.02 May 13, 2004
Code Address: 85C4B000h Length: 00012DD8h
Data Address: 85BAD000h Length: 00001380h
IPXRTRNM.NLM IPX Router Network Management
Version 6.60 June 24, 1998
Code Address: 85B7F000h Length: 0000C223h
Data Address: 85B8D000h Length: 000043C0h
NMAS.NLM Novell Modular Authentication Service
Version 2.68 June 17, 2004
Code Address: 85B17000h Length: 000333C8h
Data Address: 85B4C000h Length: 00007AD0h
SPMNWCC.NLM Novell SPM Client for NWCC
Version 1.01 May 13, 2004
Code Address: 85B02000h Length: 00010B58h
Data Address: 85B14000h Length: 00001340h
IPXRTR.NLM IPX NLSP Router Production_02Dec2001
Version 6.70.01 December 3, 2001
Code Address: 85BB5000h Length: 00047B7Eh
Data Address: 85BFE000h Length: 00017B10h
GAMS.NLM Graded Authentication Management Service
Version 1.03 April 28, 2004
Code Address: 85AF3000h Length: 0000D867h
Data Address: 85080000h Length: 000012B8h
NSPDNS.NLM NetWare Winsock 2.0 NSPDNS.NLM Name Service Providers
Version 6.20.03 September 8, 2003
Code Address: 84529000h Length: 00002527h
Data Address: 85884000h Length: 000004E4h
SLPTCP.NLM SERVICE LOCATION TCP/UDP INTERFACE (RFC2165/RFC2608)
Version 2.09 April 15, 2004
Code Address: 85076000h Length: 0000385Ah
Data Address: 8507B000h Length: 0000108Ch
WSPIP.NLM NetWare Winsock Service 1.0 NLM for TCP and UDP
Version 6.21.04 June 4, 2004
Code Address: 85497000h Length: 0000F024h
Data Address: 854A8000h Length: 0000226Ch
NCPIP.NLM NetWare NCP Services over IP
Version 6.01 June 8, 2004
Code Address: 85023000h Length: 00016289h
Data Address: 8503B000h Length: 000032C0h
BSDSOCK.NLM Novell BSDSOCK Module
Version 6.57.04 June 18, 2004
Code Address: 857E1000h Length: 00010C59h
Data Address: 857F3000h Length: 0000C0E0h
TCPIP.NLM Novell TCP/IP Stack - Network module (NULL encryption)
Version 6.57.06 June 1, 2004
Code Address: 85108000h Length: 0004D8DCh
Data Address: 85157000h Length: 00038160h
TCP.NLM Novell TCP/IP Stack - Transport module (NULL encryption)
Version 6.57.03 March 23, 2004
Code Address: 851BA000h Length: 00024C3Bh
Data Address: 852C5000h Length: 0007DDF0h
NETLIB.NLM Novell TCPIP NETLIB Module
Version 6.50.22 February 12, 2003
Code Address: 851E2000h Length: 00005AACh
Data Address: 851E9000h Length: 000D0710h
CSLIND.NLM TCPIP CSL INDEPENDENCE MODULE 7Dec99 7Dec99
Version 4.21 December 7, 1999
Code Address: 850BF000h Length: 000003CCh
Data Address: 850C1000h Length: 000024E0h
LSAPI.NLM NLS LSAPI Library
Version 5.02 January 7, 2003
Code Address: 85004000h Length: 0000A51Bh
Data Address: 85010000h Length: 00001B00h
NLSAPI.NLM NLSAPI
Version 5.02 August 7, 2003
Code Address: 84F81000h Length: 000124DBh
Data Address: 84F95000h Length: 000022A4h
CE1000.LAN Intel(R) PRO/1000 Network Connections Driver
Version 7.34 March 12, 2004
Code Address: 84F19000h Length: 00012913h
Data Address: 0066F000h Length: 00007491h
ETHERTSM.NLM Novell Ethernet Topology Specific Module
Version 3.89 January 27, 2003
Code Address: 8400F000h Length: 000024D7h
Data Address: 839D9000h Length: 000002BCh
MSM.NLM Novell Multi-Processor Media Support Module
Version 4.10 January 24, 2003
Code Address: 84F09000h Length: 0000E5B3h
Data Address: 83FEC000h Length: 00003DCCh
CONNAUD.NLM NLS - Connection Metering
Version 3.15 May 12, 2004
Code Address: 84B1C000h Length: 00003453h
Data Address: 84B21000h Length: 00000A9Ch
NLSMETER.NLM NLS - Software Usage Metering Database
Version 3.41 February 19, 2004
Code Address: 84AF4000h Length: 0000E4D7h
Data Address: 84B04000h Length: 0000759Ch
NLSLSP.NLM NLS - License Service Provider
Version 5.02 March 16, 2004
Code Address: 84E77000h Length: 0006A5A7h
Data Address: 84EE3000h Length: 0001F75Ch
IPXS.NLM NetWare STREAMS IPX Protocol
Version 4.10.01 February 12, 1998
Code Address: 84E2B000h Length: 00001C95h
Data Address: 84E2E000h Length: 000000ECh
Global Code Address: 84E30000h Length: 00001000h
CSL.NLM NetWare Call Support Layer For NetWare
Version 2.06.02 January 13, 2000
Code Address: 83FB4000h Length: 0000CB32h
Data Address: 83FC2000h Length: 000028F4h
BTRIEVE.NLM BTRIEVE.NLM v7.90.000
Version 7.90 March 21, 2001
Code Address: 83FA7000h Length: 000013BFh
Data Address: 83FAA000h Length: 00000980h
NWMKDE.NLM NWMKDE.NLM v7.94.251.000
Version 7.94 December 11, 2001
Code Address: 84403000h Length: 00053D55h
Data Address: 84458000h Length: 0000F784h
NWENC103.NLM NWENC103.NLM v7.90.000 (Text Encoding Conversion Library)
Version 7.90 February 24, 2001
Code Address: 846AC000h Length: 0004D0F5h
Data Address: 846FB000h Length: 001B0208h
NWAIF103.NLM nwaif103.nlm v7.94, Build 251 ()
Version 7.94 November 30, 2001
Code Address: 843B3000h Length: 00010E51h
Data Address: 842ED000h Length: 00006828h
PSVCS.NLM Portability Services
Version 251.00 November 30, 2001
Code Address: 8435D000h Length: 0001270Fh
Data Address: 84371000h Length: 00009464h
NWUCMGR.NLM NWUCMGR.NLM v1.5 Build 230
Version 1.05 March 14, 2001
Code Address: 84013000h Length: 0000D920h
Data Address: 84022000h Length: 000078D4h
SNMP.NLM Netware 4.x/5.x/6.x SNMP Service
Version 4.17 January 23, 2004
Code Address: 83E6C000h Length: 00014070h
Data Address: 83E82000h Length: 000031E0h
TLI.NLM NetWare Transport Level Interface Library
Version 4.30.02 December 19, 2000
Code Address: 83E50000h Length: 00003859h
Data Address: 83E55000h Length: 00000164h
Global Code Address: 83E57000h Length: 00001000h
Global Data Address: 83E59000h Length: 00002000h
NSPSAP.NLM NetWare Winsock 2.0 NLM NSPSAP.NLM Name Service Provider
Version 6.20.02 September 8, 2003
Code Address: 83DC8000h Length: 00001EE7h
Data Address: 83DCB000h Length: 00000610h
CONLOG.NLM System Console Logger
Version 3.00.02 November 26, 2002
Code Address: 83DB7000h Length: 000020DCh
Data Address: 83DBB000h Length: 00001CC0h
NCPIPX.NLM Novell NCP/IPX Stack NLM
Version 5.60 January 22, 2004
Code Address: 83D71000h Length: 000056BFh
Data Address: 83D78000h Length: 00001308h
WSPIPX.NLM NetWare Winsock Service 1.0 NLM for IPX and SPX
Version 6.21 March 22, 2004
Code Address: 83D86000h Length: 0000DB09h
Data Address: 83D95000h Length: 00001762h
IPXSPX.NLM NetWare IPX/SPX Protocol Stack NLM
Version 5.60 November 21, 2001
Code Address: 83D50000h Length: 0000FC52h
Data Address: 83D62000h Length: 00009A3Ah
DHOST.NLM Novell DHost Portability Interface 1.0.0 SMP
Version 10010.94 November 3, 2003
Code Address: 83CAD000h Length: 00006631h
Data Address: 839FF000h Length: 0000234Ch
NSPNDS.NLM NetWare Winsock 2.0 NSPNDS.NLM Name Service Provider
Version 6.20 November 12, 2001
Code Address: 83CB7000h Length: 00006547h
Data Address: 839FD000h Length: 00000518h
CALNLM32.NLM NetWare NWCalls Runtime Library
Version 6.00 June 3, 2004
Code Address: 83CEA000h Length: 0001B649h
Data Address: 83462000h Length: 00000510h
DS.NLM Novell eDirectory Version 8.7.3.2 SMP
Version 10551.13 May 26, 2004
Code Address: 84041000h Length: 00258D34h
Data Address: 83913000h Length: 0007697Ch
ROLLCALL.NLM RollCall NLM (101, API 1.0)
Version 5.00 July 27, 1998
Code Address: 8390F000h Length: 0000055Dh
Data Address: 83911000h Length: 000002D4h
SAL.NLM Novell System Abstraction Layer Version 2.2.0
Version 20210.73 November 10, 2003
Code Address: 8388F000h Length: 00007946h
Data Address: 8368F000h Length: 00001230h
NDSAUDIT.NLM Directory Services Audit
Version 2.09 May 22, 2003
Code Address: 83677000h Length: 00010844h
Data Address: 83689000h Length: 00002ED0h
POLIMGR.NLM NetWare License Policy Manager
Version 6.22 February 27, 2004
Code Address: 838EE000h Length: 00013C2Ch
Data Address: 83885000h Length: 00008D68h
TIMESYNC.NLM NetWare Time Synchronization Services
Version 6.60.11 May 13, 2004
Code Address: 83832000h Length: 0000DE1Ch
Data Address: 83714000h Length: 00004200h
CLXNLM32.NLM NetWare NWCLX Runtime Library
Version 6.00 June 3, 2004
Code Address: 836DC000h Length: 00001213h
Data Address: 83707000h Length: 000001B0h
DSAPI.NLM NetWare NWNet Runtime Library
Version 5.05.08 March 9, 2004
Code Address: 836D8000h Length: 00000043h
Data Address: 836DA000h Length: 00000024h
DSEVENT.NLM NetWare DSEvent Runtime Library
Version 5.05.08 March 1, 2004
Code Address: 836D4000h Length: 00000633h
Data Address: 836D6000h Length: 00000034h
NETNLM32.NLM NetWare NWNet Runtime Library
Version 5.05.08 March 9, 2004
Code Address: 838B8000h Length: 00034ED7h
Data Address: 836CE000h Length: 00004D45h
NCPNLM32.NLM NetWare NWNCP Runtime Library
Version 6.00 June 3, 2004
Code Address: 83898000h Length: 0001E1C3h
Data Address: 00000000h Length: 00000000h
CLNNLM32.NLM NetWare NWClient Runtime Library
Version 6.00 June 3, 2004
Code Address: 836C9000h Length: 00001C72h
Data Address: 836CC000h Length: 00000130h
CLIB.NLM (Legacy) Standard C Runtime Library for NLMs
Version 5.90.10 February 24, 2004
Code Address: 836E9000h Length: 0001898Eh
Data Address: 83703000h Length: 00002FB0h
NIT.NLM NetWare Interface Tools Library for NLMs
Version 5.90.10 February 24, 2004
Code Address: 83814000h Length: 0001C694h
Data Address: 83710000h Length: 00000690h
NLMLIB.NLM Novell NLM Runtime Library
Version 5.90.10 February 24, 2004
Code Address: 837E7000h Length: 0002630Dh
Data Address: 8380F000h Length: 000038C0h
STREAMS.NLM NetWare STREAMS PTF
Version 6.00.04 October 25, 2002
Code Address: 837D3000h Length: 000120CDh
Data Address: 8373D000h Length: 000010A0h
Global Code Address: 83740000h Length: 00001000h
REQUESTR.NLM Novell NCP Requestor for NLMs
Version 5.90.10 February 24, 2004
Code Address: 8375F000h Length: 00020BF3h
Data Address: 83781000h Length: 000010B0h
THREADS.NLM Novell Threads Package for NLMs
Version 5.90.10 February 24, 2004
Code Address: 837A6000h Length: 00018BD8h
Data Address: 837C0000h Length: 00011660h
LIB0.NLM Novell Ring 0 Library for NLMs
Version 5.90.10 February 24, 2004
Code Address: 83A0D000h Length: 0002527Ah
Data Address: 83A34000h Length: 00228050h
MASV.NLM Mandatory Access Control Service
Version 1.39.01 March 13, 2002
Code Address: 83695000h Length: 0000EE86h
Data Address: 8365E000h Length: 00002390h
NSPSLP.NLM NetWare Winsock 2.0 NSPSLP.NLM Name Service Provider
Version 6.20.02 September 8, 2003
Code Address: 83668000h Length: 00005ED3h
Data Address: 8366F000h Length: 00000B30h
PMLODR.NLM PMLodr for NW65
Version 1.25 May 30, 2003
Code Address: 8364B000h Length: 0000E54Ah
Data Address: 8365B000h Length: 00001630h
SLP.NLM SERVICE LOCATION PROTOCOL (RFC2165/RFC2608)
Version 2.09 April 15, 2004
Code Address: 83628000h Length: 0001A368h
Data Address: 834B1000h Length: 00005354h
DSLOADER.NLM Novell eDirectory Version 8.7.3 Loader SMP
Version 10551.13 May 26, 2004
Code Address: 83418000h Length: 0000C76Ch
Data Address: 83426000h Length: 00001224h
XIM.XLM Novell NICI Signed Loader
Version 26410.07 June 15, 2004
Code Address: 82F90000h Length: 00020790h
Data Address: 0009A000h Length: 000039B8h
WS2_32.NLM NetWare Winsock 2.0 NLM
Version 6.21.06 June 15, 2004
Code Address: 82DD3000h Length: 00036C68h
Data Address: 82E0B000h Length: 00011654h
NCP.NLM NetWare Core Protocol (NCP) Engine
Version 5.60 June 15, 2004
Code Address: 82E24000h Length: 00026B2Fh
Data Address: 82E4C000h Length: 00018B24h
QUEUE.NLM NetWare Queue Services NLM
Version 5.60 May 24, 2001
Code Address: 82DC7000h Length: 00006D8Dh
Data Address: 82DCF000h Length: 00000473h
MALHLP.NLM NSS Configure help messages (Build 417 MP)
Version 3.22 May 10, 2004
Code Address: 8019F000h Length: 000000BAh
Data Address: 801A1000h Length: 0000002Ah
CDDVD.NSS NSS Loadable Storage System (LSS) for CD/UDF (Build 254 MP)
Version 3.22 June 11, 2004
Code Address: 801BA000h Length: 00013160h
Data Address: 800CF000h Length: 00001060h
NSSIDK.NSS NSS Pool Configuration Manager (Build 432 MP)
Version 3.22 May 14, 2004
Code Address: 800F8000h Length: 00003725h
Data Address: 800FD000h Length: 00000090h
PARTAPI.NLM Partition APIs for NetWare 6.1
Version 2.00 April 17, 2002
Code Address: 800AF000h Length: 00000007h
Data Address: 00000000h Length: 00000000h
VOLMN.NSS NSS Distributed Volume Manager (Build 394 MP)
Version 3.22 May 14, 2004
Code Address: 800E0000h Length: 00009FE3h
Data Address: 800AD000h Length: 000005B0h
NWSA.NSS NSS NetWare Semantic Agent (NWSA) (Build 1301 MP)
Version 3.22 June 16, 2004
Code Address: 80155000h Length: 00048A4Eh
Data Address: 80487000h Length: 0009D310h
ZLSS.NSS NSS Journaled Storage System (ZLSS) (Build 1798 MP)
Version 3.22 June 7, 2004
Code Address: 803C4000h Length: 000C1DE6h
Data Address: 800B9000h Length: 0000BC30h
MAL.NSS NSS Media Access Layer (MAL) (Build 599 MP)
Version 3.22 May 14, 2004
Code Address: 800B1000h Length: 00002F76h
Data Address: 800B5000h Length: 00000170h
MANAGE.NSS NSS Management Functions (Build 617 MP)
Version 3.22 June 4, 2004
Code Address: 80106000h Length: 00049605h
Data Address: 80151000h Length: 00000C00h
COMN.NSS NSS Common Support Layer (COMN) (Build 2756 MP)
Version 3.22 May 28, 2004
Code Address: 801D1000h Length: 000D5ADBh
Data Address: 802A8000h Length: 00015B10h
NSS.NLM NSS (Novell Storage Services) (Build 977 MP)
Version 3.22 May 14, 2004
Code Address: B7C74000h Length: 0002C820h
Data Address: B7EEA000h Length: 00091480h
SYSLOG.NLM NetWare Logfile Daemon
Version 6.05.02 November 3, 2003
Code Address: B7CA8000h Length: 00005E6Ah
Data Address: B7CAF000h Length: 000260E4h
LIBNSS.NLM Generic Library used by NSS (Build 187 MP)
Version 3.22 May 10, 2004
Code Address: B7C6C000h Length: 000042DCh
Data Address: B7C72000h Length: 000003D0h
NSSWIN.NLM NSS ASCI Window API Library (Build 204 MP)
Version 3.22 May 10, 2004
Code Address: B7C62000h Length: 000047DCh
Data Address: B7C68000h Length: 000000FCh
LOCNLM32.NLM NetWare NWLocale Runtime Library
Version 6.00 June 3, 2004
Code Address: B7C52000h Length: 0000458Bh
Data Address: B7C58000h Length: 00000B80h
UNICODE.NLM NetWare Unicode Runtime Library (UniLib-based) [optimized]
Version 7.00 June 3, 2004
Code Address: B7C47000h Length: 000016D5h
Data Address: B7C4A000h Length: 00000504h
FILESYS.NLM NetWare File System NLM
Version 5.13 April 2, 2004
Code Address: B7D18000h Length: 0008DEB7h
Data Address: B7C21000h Length: 00012C80h
LFS.NLM NetWare Logical File System NLM
Version 5.12 January 23, 2004
Code Address: B7BDF000h Length: 000094EDh
Data Address: B7BEA000h Length: 000084BCh
CONNMGR.NLM NetWare Connection Manager NLM
Version 5.60 June 16, 2004
Code Address: B7BF6000h Length: 00011475h
Data Address: B7C09000h Length: 00003C78h
ACPIPWR.NLM ACPI Power Management Driver for ACPI compliant systems
Version 1.04 June 1, 2004
Code Address: B7A31000h Length: 00000C18h
Data Address: B7BD3000h Length: 0000091Ch
ACPICMGR.NLM ACPI Component Manager for ACPI compliant systems
Version 1.04 June 1, 2004
Code Address: B7A41000h Length: 00000AFCh
Data Address: B7A43000h Length: 00000344h
ADPT160M.HAM Adaptec Ultra160 Host Adapter Module
Version 18.31.13 November 19, 2003
Code Address: B7B9B000h Length: 0002001Fh
Data Address: 7A39A000h Length: 00003860h
PEDGE3.HAM PERC 3/SC/DC(L)/QC, 4/SC/DC/Di, 4e/SC/DC/Di/Si & CERC HAM Driver.
Version 7.01.24 April 13, 2004
Code Address: B7B78000h Length: 00008612h
Data Address: 7A3C5000h Length: 00004744h
IDEATA.HAM Novell ATA/IDE/ATAPI Host Adapter Module
Version 4.15 June 4, 2004
Code Address: B7B58000h Length: 0000C911h
Data Address: 7A3ED000h Length: 0000429Ch
QLCSFTE.CDM QLogic SCSI Enclosure SAF-TE Processor CDM
Version 1.00.01 May 24, 2000
Code Address: B7B55000h Length: 000010DEh
Data Address: 7A415000h Length: 00000034h
SCSIHD.CDM Novell NetWare SCSI Fixed Disk Custom Device Module
Version 3.02.06 April 21, 2004
Code Address: B7B4F000h Length: 00004A4Eh
Data Address: 7A454000h Length: 00000DB0h
IDECD.CDM Novell ATAPI CD-ROM/DVD-ROM Custom Device Module
Version 4.00 April 24, 2004
Code Address: B7AC2000h Length: 00003978h
Data Address: 7A4D6000h Length: 00000AECh
ACPIDRV.PSM ACPI Platform Support Module for ACPI compliant systems
Version 1.04 June 1, 2004
Code Address: B7A49000h Length: 0000A8C2h
Data Address: 7A4DD000h Length: 0000BD34h
ACPICA.NLM ACPI Component Architecture for ACPI compliant systems
Version 1.04 June 1, 2004
Code Address: B79B7000h Length: 0002D17Ah
Data Address: B79E6000h Length: 0001158Ah
ACPIASL.NLM ACPI Architecture Services Layer for ACPI compliant systems
Version 1.04 June 1, 2004
Code Address: B7985000h Length: 00000F9Bh
Data Address: B7987000h Length: 000001DCh
UMSSHIM.NLM Novell USB Mouse Shim
Version 1.03 November 19, 2003
Code Address: B78FE000h Length: 00000B59h
Data Address: 7A4EB000h Length: 00000428h
UKBDSHIM.NLM Novell USB Keyboard Shim
Version 1.03 November 19, 2003
Code Address: B78EA000h Length: 00000FD1h
Data Address: 7A4EC000h Length: 000005C4h
EHCIDRV.CAD Novell Universal Serial Bus EHCI driver
Version 1.02 May 10, 2004
Code Address: B7026000h Length: 00005B6Fh
Data Address: 7A500000h Length: 00001B58h
UHCIDRV.CAD Novell Universal Serial Bus UHCI driver
Version 1.04 May 10, 2004
Code Address: B7038000h Length: 00004B99h
Data Address: 7A520000h Length: 000006CCh
CIOSMLID.CLS Novell CIOS MLID Driver
Version 1.00 May 28, 2003
Code Address: B7031000h Length: 0000539Ah
Data Address: 7A521000h Length: 0000143Ch
LSL.NLM Novell NetWare Link Support Layer
Version 4.81 May 7, 2004
Code Address: B7051000h Length: 0000A617h
Data Address: B705D000h Length: 00009EC8h
CIOS.NLM Consolidated IO System
Version 1.21 May 10, 2004
Code Address: B6FB8000h Length: 0004D6C2h
Data Address: 3DF7C000h Length: 0001BC5Ah
NWPALOAD.NLM NetWare 5 NWPA Load Utility
Version 3.00 July 10, 2000
Code Address: B6E1F000h Length: 00000007h
Data Address: 00000000h Length: 00000000h
NWPA.NLM NetWare 6.5 NetWare Peripheral Architecture NLM
Version 3.20.04 May 7, 2004
Code Address: B6F04000h Length: 00016906h
Data Address: B6E44000h Length: 000029B0h
MM.NLM NetWare 6.5 Media Manager
Version 3.20.10 June 15, 2004
Code Address: B6E57000h Length: 00047E22h
Data Address: B6DF6000h Length: 0000B378h
SGUID.NLM NetWare GUID Services
Version 6.01 September 27, 2002
Code Address: B6D80000h Length: 00000E04h
Data Address: B6DF4000h Length: 0000018Ah
NBI.NLM NetWare Bus Interface
Version 3.00.04 June 9, 2004
Code Address: B6E0B000h Length: 0000D16Dh
Data Address: B6D78000h Length: 00003C9Dh
NEB.NLM Novell Event Bus
Version 5.60 December 11, 2002
Code Address: B6D82000h Length: 00005843h
Data Address: B6D89000h Length: 0000097Ch
DIAG500.NLM Diagnostic/coredump utility for NetWare 5.x/6.x
Version 3.00 May 11, 2004
Code Address: B6D5D000h Length: 00006CF0h
Data Address: B6DA0000h Length: 0001D90Ch
CPUCHECK.NLM NetWare Processor Checking Utility
Version 5.60.01 October 21, 2003
Code Address: B6D6F000h Length: 00001A04h
Data Address: B6D72000h Length: 00004B0Ch
NWKCFG.NLM NetWare Kernel Config NLM
Version 2.16 April 7, 2004
Code Address: B6D53000h Length: 00003EEFh
Data Address: B6D58000h Length: 00003CA4h
CDBE.NLM NetWare Configuration DB Engine
Version 6.01 May 10, 2004
Code Address: B6AC1000h Length: 00011466h
Data Address: B6AD4000h Length: 000160A2h
FATFS.NLM FAT Filesystem Module for NetWare
Version 1.13 June 2, 2004
Code Address: B627F000h Length: 00023CCEh
Data Address: B62A4000h Length: 0002F68Fh
CIOSSHIM.NLM Novell CIOS Platform Shim
Version 1.11 March 26, 2004
Code Address: B6213000h Length: 000033E7h
Data Address: B6218000h Length: 000058ECh
LIBC.NLM Standard C Runtime Library for NLMs [optimized, 5]
Version 7.05 June 23, 2004
Code Address: B6323000h Length: 000B35B6h
Data Address: B0179000h Length: 0003D816h
PVER500.NLM NetWare 6.XX Version Library
Version 3.00 February 25, 2003
Code Address: B016B000h Length: 0000068Fh
Data Address: B016D000h Length: 00000360h
SERVER.NLM NetWare Server Operating System
Version 5.70.02 June 11, 2004
Code Address: 002047E0h Length: 0015610Ah
Data Address: 004047E0h Length: 001C7820h
Server MOM halted Tuesday, October 25, 2011 11:45:30.404 am
Abend 1 on P00: Server-5.70.02-0: NCPIP: ReplyDisgard overflowed reply buffer!!
Registers:
CS = 0008 DS = 0068 ES = 0068 FS = 0068 GS = 007B SS = 0068
EAX = 00000002 EBX = 000005EF ECX = 000005E7 EDX = 90247000
ESI = 000005EF EDI = 00000001 EBP = 00000008 ESP = B706AF4C
EIP = 85070318 FLAGS = 00200206
85070318 83C404 ADD ESP, 00000004
EIP in NCPIP.NLM at code start +00003318h
The violation occurred while processing the following instruction:
85070318 83C404 ADD ESP, 00000004
8507031B 8B44240C MOV EAX, [ESP+0C]
8507031F 6AFE PUSH FE
85070321 83C00C ADD EAX, 0000000C
85070324 50 PUSH EAX
85070325 E846D3097B CALL SERVER.NLM|atomic_and
8507032A 83C408 ADD ESP, 00000008
8507032D 8B44240C MOV EAX, [ESP+0C]
85070331 F6400D TEST byte ptr [EAX+0D]
85070334 0174518B ADD [ECX+EDX*2-75], ESI
Running process: Server 00:3 Process
Thread Owned by NLM: SERVER.NLM
Stack pointer: B706BF60
OS Stack limit: B7064020
Scheduling priority: 67371008
Wait state: 50500F0 Waiting for work
Stack: -85085BDC (NCPIP.NLM|(Data Start)+BDC)
--9024708E ?
--9024708E ?
--902470DC ?
--90247000 ?
--B706BF00 (EHCIDRV.CAD|EHCIDebugDumpRegs+9550)
--902470DC ?
--902470B4 ?
--902476C3 ?
80184219 (NWSA.NSS|NSSCase89+459)
--902470B4 ?
--00000000 ?
--00000001 ?
--902470DC ?
--000005E7 ?
B7C9E4EF (NSS.NLM|NSSMPK_UnlockNss+1F)
-B7F35C68 (NSS.NLM|NSSMPK_spinlock+0)
--00000000 ?
--B706B054 (EHCIDRV.CAD|EHCIDebugDumpRegs+86A4)
8028DAE5 (COMN.NSS|zGetInfo+A5)
--00000000 ?
--B706B0B4 (EHCIDRV.CAD|EHCIDebugDumpRegs+8704)
--00000000 ?
--00000000 ?
--2CEC1D20 ?
--3DEABEC0 ?
--00000001 ?
--B706B798 (EHCIDRV.CAD|EHCIDebugDumpRegs+8DE8)
--000004BC ?
--00000000 ?
--00000001 ?
--B706B0B4 (EHCIDRV.CAD|EHCIDebugDumpRegs+8704)
--00000000 ?
--00000000 ?
--00000050 ?
--00000000 ?
--00000001 ?
--00000000 ?
--B00771A0 ?
--00000001 ?
--B706B0B4 (EHCIDRV.CAD|EHCIDebugDumpRegs+8704)
--00000001 ?
--00000000 ?
--B706B028 (EHCIDRV.CAD|EHCIDebugDumpRegs+8678)
B633BB16 (LIBC.NLM|VerifyPathInfo+216)
--00000001 ?
--FFFFFFFF (LOADER.NLM|KernelTempAliasesEnd+FFF)
--B706B0B4 (EHCIDRV.CAD|EHCIDebugDumpRegs+8704)
--B706B750 (EHCIDRV.CAD|EHCIDebugDumpRegs+8DA0)
--B706B080 (EHCIDRV.CAD|EHCIDebugDumpRegs+86D0)
--B706B54A (EHCIDRV.CAD|EHCIDebugDumpRegs+8B9A)
--00000000 ?
-82E3EBC8 (WS2_32.NLM|ProtocolPath+0)
--B007B8C0 ?
-82E3EBC8 (WS2_32.NLM|ProtocolPath+0)
--B706B054 (EHCIDRV.CAD|EHCIDebugDumpRegs+86A4)
--B007B8C0 ?
--87D8C9A5 ?
--B0075AC0 ?
B633C721 (LIBC.NLM|BuildUnicodePath+161)
--FFFFFFFF (LOADER.NLM|KernelTempAliasesEnd+FFF)
--B0075AD2 ?
--87D8C9A5 ?
--00000001 ?
--00000000 ?
--B706B768 (EHCIDRV.CAD|EHCIDebugDumpRegs+8DB8)
--B706BC70 (EHCIDRV.CAD|EHCIDebugDumpRegs+92C0)
B634DFA7 (LIBC.NLM|kgFileOpenEx+517)
--82F03B9F ?
--B706BC70 (EHCIDRV.CAD|EHCIDebugDumpRegs+92C0)
--00000001 ?
--00000000 ?
--ECF04369 ?
B634E89C (LIBC.NLM|kgFileOpenEx+E0C)
--B0075AC0 ?
--87D8C6E0 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
-00535953 (SERVER.NLM|RDebugPollTimeoutTimer+D77F)
--00000000 ?
--00000000 ?
--00000000 ?
--5C435445 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
Additional Information:
The NetWare OS detected a problem with the system while executing a process owned by NCPIP.NLM. It may be the source of the problem or there may have been a memory corruption.
There was another long list that I omitted to save space and actually be able to post this. I can post that if need be.SERVER.NLM NetWare Server Operating System
Version 5.70.02 June 11, 2004
Your server appears to be on SP2. Please apply the current SP, nw65sp8. -
Can any one tell me how to handle interfaces in ABAP.
i would like to know what r all methodology or technology we can use like RFC,IDOC,BAPI,ALE,BDC.
Thanks in advanceHI ,
<b>BATCH DATA COMMUNICATION</b>
About Data Transfer In R/3 System
When a company decides to implement the SAP R/3 to manage business-critical data, it usually does not start from a no-data situation. Normally, a SAP R/3 project comes into replace or complement existing application.
In the process of replacing current applications and transferring application data, two situations might occur:
The first is when application data to be replaced is transferred at once, and only once.
The second situation is to transfer data periodically from external systems to SAP and vice versa.
There is a period of time when information has to be transferred from existing application, to SAP R/3, and often this process will be repetitive.
The SAP system offers two primary methods for transferring data into SAP systems. From non-SAP systems or legacy system. These two methods are collectively called batch input or batch data communication.
1. SESSION METHOD
2. CALL TRANSACTION
3. DIRECT INPUT
Advantages offered by BATCH INPUT method:
1. Can process large data volumes in batch.
2. Can be planned and submitted in the background.
3. No manual interaction is required when data is transferred.
4. Data integrity is maintained as whatever data is transferred to the table is through transaction. Hence batch input data is submitted to all the checks and validations.
To implement one of the supported data transfers, you must often write the program that exports the data from your non-SAP system. This program, known as a data transfer program must map the data from the external system into the data structure required by the SAP batch input program.
The batch input program must build all of the input to execute the SAP transaction.
Two main steps are required:
To build an internal table containing every screen and every field to be filled in during the execution of an SAP transaction.
To pass the table to SAP for processing.
Prerequisite for Data Transfer Program
Writing a Data Transfer Program involves following prerequisites:
Analyzing data from local file
Analyzing transaction
Analyzing transaction involves following steps:
The transaction code, if you do not already know it.
Which fields require input i.e., mandatory.
Which fields can you allow to default to standard values.
The names, types, and lengths of the fields that are used by a transaction.
Screen number and Name of module pool program behind a particular transaction.
To analyze a transaction::
Start the transaction by menu or by entering the transaction code in the command box.
(You can determine the transaction name by choosing System Status.)
Step through the transaction, entering the data will be required for processing your batch input data.
On each screen, note the program name and screen (dynpro) number.
(dynpro = dyn + pro. Dyn = screen, pro = number)
Display these by choosing System Status. The relevant fields are Program (dynpro) and Dynpro number. If pop-up windows occur during execution, you can get the program name and screen number by pressing F1 on any field or button on the screen.
The technical info pop-up shows not only the field information but also the program and screen.
For each field, check box, and radio button on each screen, press F1 (help) and then choose Technical Info.
Note the following information:
- The field name for batch input, which youll find in its own box.
- The length and data type of the field. You can display this information by double clicking on the Data Element field.
Find out the identification code for each function (button or menu) that you must execute to process the batch-input data (or to go to new screen).
Place the cursor on the button or menu entry while holding down the left mouse button. Then press F1.
In the pop-up window that follows, choose Technical info and note the code that is shown in the Function field.
You can also run any function that is assigned to a function key by way of the function key number. To display the list of available function keys, click on the right mouse button. Note the key number that is assigned to the functions you want to run.
Once you have program name, screen number, field name (screen field name), you can start writing.
DATA TRANSFER program.
Declaring internal table
First Integral Table similar to structure like local file.
Declaring internal table like BDCDATA
The data from internal table is not transferred directly to database table, it has to go through transaction. You need to pass data to particular screen and to particular screen-field. Data is passed to transaction in particular format, hence there is a need for batch input structure.
The batch input structure stores the data that is to be entered into SAP system and the actions that are necessary to process the data. The batch input structure is used by all of the batch input methods. You can use the same structure for all types of batch input, regardless of whether you are creating a session in the batch input queue or using CALL TRANSACTION.
This structure is BDCDATA, which can contain the batch input data for only a single run of a transaction. The typical processing loop in a program is as follows:
Create a BDCDATA structure
Write the structure out to a session or process it with CALL TRANSACTION USING; and then
Create a BDCDATA structure for the next transaction that is to be processed.
Within a BDCDATA structure, organize the data of screens in a transaction. Each screen that is processed in the course of a transaction must be identified with a BDCDATA record. This record uses the Program, Dynpro, and Dynbegin fields of the structure.
The screen identifier record is followed by a separate BDCDATA record for each value, to be entered into a field. These records use the FNAM and FVAL fields of the BDCDATA structure. Values to be entered in a field can be any of the following:
Data that is entered into screen fields.
Function codes that are entered into the command field. Such function codes execute functions in a transaction, such as Save or Enter.
The BDCDATA structure contains the following fields:
PROGRAM: Name of module pool program associated with the screen. Set this field only for the first record for the screen.
DYNPRO: Screen Number. Set this field only in the first record for the screen.
DYNBEGIN: Indicates the first record for the screen. Set this field to X, only for the first record for the screen. (Reset to (blank) for all other records.)
FNAM: Field Name. The FNAM field is not case-sensitive.
FVAL: Value for the field named in FNAM. The FVAL field is case-sensitive. Values assigned to this field are always padded on the right, if they are less than 132 characters. Values must be in character format.
Transferring data from local file to internal table
Data is uploaded to internal table by UPLOAD of WS_UPLOAD function.
Population of BDCDATA
For each record of internal table, you need to populate Internal table, which is similar to BDCDATA structure.
All these five initial steps are necessary for any type of BDC interface.
DATA TRANSFER program can call SESSION METHOD or CALL TRANSACTION. The initial steps for both the methods are same.
First step for both the methods is to upload the data to internal table. From Internal Table, the data is transferred to database table by two ways i.e., Session method and Call transaction.
<b>SESSION METHOD</b>
About Session method
In this method you transfer data from internal table to database table through sessions.
In this method, an ABAP/4 program reads the external data that is to be entered in the SAP System and stores the data in session. A session stores the actions that are required to enter your data using normal SAP transaction i.e., Data is transferred to session which in turn transfers data to database table.
Session is intermediate step between internal table and database table. Data along with its action is stored in session i.e., data for screen fields, to which screen it is passed, the program name behind it, and how the next screen is processed.
When the program has finished generating the session, you can run the session to execute the SAP transactions in it. You can either explicitly start and monitor a session or have the session run in the background processing system.
Unless session is processed, the data is not transferred to database table.
<b>BDC_OPEN_GROUP</b>
You create the session through program by BDC_OPEN_GROUP function.
Parameters to this function are:
User Name: User name
Group: Name of the session
Lock Date: The date on which you want to process the session.
Keep: This parameter is passed as X when you want to retain session after
processing it or to delete it after processing.
<b>BDC_INSERT</b>
This function creates the session & data is transferred to Session.
Parameters to this function are:
Tcode: Transaction Name
Dynprotab: BDC Data
<b>BDC_CLOSE_GROUP</b>
This function closes the BDC Group. No Parameters.
Some additional information for session processing
When the session is generated using the KEEP option within the BDC_OPEN_GROUP, the system always keeps the sessions in the queue, whether it has been processed successfully or not.
However, if the session is processed, you have to delete it manually. When session processing is completed successfully while KEEP option was not set, it will be removed automatically from the session queue. Log is not removed for that session.
If the batch-input session is terminated with errors, then it appears in the list of INCORRECT session and it can be processed again. To correct incorrect session, you can analyze the session. The Analysis function allows to determine which screen and value has produced the error. If you find small errors in data, you can correct them interactively, otherwise you need to modify batch input program, which has generated the session or many times even the data file.
<b>CALL TRANSACTION</b>
About CALL TRANSACTION
A technique similar to SESSION method, while batch input is a two-step procedure, Call Transaction does both steps online, one after the other. In this method, you call a transaction from your program by
Call transaction <tcode> using <BDCTAB>
Mode <A/N/E>
Update <S/A>
Messages into <MSGTAB>.
Parameter 1 is transaction code.
Parameter 2 is name of BDCTAB table.
Parameter 3 here you are specifying mode in which you execute transaction
A is all screen mode. All the screen of transaction are displayed.
N is no screen mode. No screen is displayed when you execute the transaction.
E is error screen. Only those screens are displayed wherein you have error record.
Parameter 4 here you are specifying update type by which database table is updated.
S is for Synchronous update in which if you change data of one table then all the related Tables gets updated. And sy-subrc is returned i.e., sy-subrc is returned for once and all.
A is for Asynchronous update. When you change data of one table, the sy-subrc is returned. And then updating of other affected tables takes place. So if system fails to update other tables, still sy-subrc returned is 0 (i.e., when first table gets updated).
Parameter 5 when you update database table, operation is either successful or unsuccessful or operation is successful with some warning. These messages are stored in internal table, which you specify along with MESSAGE statement. This internal table should be declared like BDCMSGCOLL, a structure available in ABAP/4. It contains the following fields:
1. Tcode: Transaction code
2. Dyname: Batch point module name
3. Dynumb: Batch input Dyn number
4. Msgtyp: Batch input message type (A/E/W/I/S)
5. Msgspra: Batch input Lang, id of message
6. Msgid: Message id
7. MsgvN: Message variables (N = 1 - 4)
For each entry, which is updated in database, table message is available in BDCMSGCOLL. As BDCMSGCOLL is structure, you need to declare a internal table which can contain multiple records (unlike structure).
Steps for CALL TRANSACTION method
1. Internal table for the data (structure similar to your local file)
2. BDCTAB like BDCDATA
3. UPLOAD or WS_UPLOAD function to upload the data from local file to itab. (Considering file is local file)
4. Loop at itab.
Populate BDCTAB table.
Call transaction <tcode> using <BDCTAB>
Mode <A/N/E>
Update <S/A>.
Refresh BDCTAB.
Endloop.
(To populate BDCTAB, You need to transfer each and every field)
The major differences between Session method and Call transaction are as follows:
SESSION METHOD CALL TRANSACTION
1. Data is not updated in database table unless Session is processed. Immediate updation in database table.
2. No sy-subrc is returned. Sy-subrc is returned.
3. Error log is created for error records. Errors need to be handled explicitly
4. Updation in database table is always synchronous Updation in database table can be synchronous Or Asynchronous.
Error Handling in CALL TRANSACTION
When Session Method updates the records in database table, error records are stored in the log file. In Call transaction there is no such log file available and error record is lost unless handled. Usually you need to give report of all the error records i.e., records which are not inserted or updated in the database table. This can be done by the following method:
Steps for the error handling in CALL TRANSACTION
1. Internal table for the data (structure similar to your local file)
2. BDCTAB like BDCDATA
3. Internal table BDCMSG like BDCMSGCOLL
4. Internal table similar to Ist internal table
(Third and fourth steps are for error handling)
5. UPLOAD or WS_UPLOAD function to upload the data from the local file to itab. (Considering file is local file)
6. Loop at itab.
Populate BDCTAB table.
Call transaction <tr.code> using <Bdctab>
Mode <A/N/E>
Update <S/A>
Messages <BDCMSG>.
Perform check.
Refresh BDCTAB.
Endloop.
7 Form check.
IF sy-subrc <> 0. (Call transaction returns the sy-subrc if updating is not successful).
Call function Format_message.
(This function is called to store the message given by system and to display it along with record)
Append itab2.
Display the record and message.
Check these links to know more
<b>BAPI</b>
http://www.allsaplinks.com/bapi.html
<b>IDOC</b>
http://www.allsaplinks.com/idoc_sample.html
http://www.allsaplinks.com/
http://www.sap-img.com/
http://www.sappoint.com/abap.html
Regards,
Santosh -
User Interface (UI) Too Small on InDesign and CC Suite
I have a 27″ IMac running Yosemite 10.10.2. Its native screen resolution is 2560×1440.
When I opened CC Indesign 2014 for the first time I was shocked to see that the tools and rest of the user interface were SO SMALL that I was having tremendous difficulty seeing them clearly. I'm talking 5 and 6 point type!!! And the icons... minuscule!
I lowered the resolution of the display, but type then becomes fuzzy. I searched the web and found that there were others who were having the same problem.
I find it hard to believe that a company specializing in software for the design/creative community would overlook something as CRITICAL as size of the graphical user interface and its customization to work optimally on different platforms and with different display sizes and to satisfy the particular needs of each user.
The UI obviously greatly impacts our working speed and facility.
I called Adobe and their tech support could not help. I called Apple and got the same.
I've been a graphic designer for over 20 years. Frankly, at this point, I find the suite UNusable (I took a quick look at Photoshop and Illustrator and the same issue applies).
This is just unbelievable! Anyone out there have an answer?
Someone suggested we should repeat our complaints INDEPENDENTLY in the general forum instead of them being buried on one thread. GREAT IDEA!!CC 2014 has a Expermental Preference you can use to increace the UI size 200% for High resolution displays
-
Cheapo alternative to Apple Lightning to USB Camera Adapter for audio interface?
I am getting an audio interface (Steinberg UR44) which can be controlled with an iPad via the Apple Lightning USB Camera Adapter and a standard USB printer cable (Type A male to type B male), but I am too cheap to buy the ridiculously overpriced Apple adapter, so I am wondering if the following will work instead:
iPad --> Apple lighting male to USB Type A male cable (the standard charging cable) --> USB Type A female to Type B male adapter --> Audio Interface
Other adapters are available for USB Type A female to Type B micro or mini male, so the same kind of arrangement might work for cameras.
The adapters are five bucks or less vs. thirty for the RIDICULOUSLY OVERPRICED (yes, I know, I already said that) Apple adapter.
I am thinking this is a better way to go than a cheap unlicensed knockoff lightning adapter, because the critical part of the connection (the lightning plug and electronics) would still be made by Apple.
Has anyone tried the above with either an audio interface or camera?Because it was designed for use with the iPad. Apple makes no claim that it will work with an iPhone.
-
Dear all,
Hereafter is my scenario;
My customer after sales system works on AS400. Assuming that I would manage spare parts (required for after sales) inventory, including goods entry, goods issue as well as the company financial accounting in SAP, I have to interface the two system.
From SAP to AS400: (flow1) Master files + (flow2) goods entry
From AS400 to SAP: (flow3) AR postings, (flow4) goods consumption
Then my two systems will be in line in terms of referential data (flow1), stock movement (flow2 + flow4), invoicing (flow3).
1) My question is to know what would be the best way to flow2 knowing that stock movement following a goods entry (done in SAP) should be visible in real time from AS400?
2) Regarding other flows, no need for real time. So I guess flat file should be ok. However, would master data for instance sent from SAP to AS400 require a mapping table in order to be properly integrated in AS400?
Regards.Real Time doesn't mean always fast. It depends on your application requirements.
Anyway, don't think too much about Real Time in Windows. If it's possible, try to do all "time critical" operations in Matlab and after that pull data with LV. -
7206 G1 boot issue: No interface specified for interface_command
I can't seem to find out what this command means? I am pasting a config into a new router, do I need to paste in a certain order?
It boots just fine after it decompresses again, but it leaves me with a very lengthy boot time.
Core_7206_1#write mem
Building configuration...
[OK]
Core_7206_1#reload
Proceed with reload? [confirm]
*Jun 7 01:16:43.547: %SYS-5-RELOAD: Reload requested by console. Reload Reason: Reload Command.
System Bootstrap, Version 12.3(4r)T3, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 2004 by cisco Systems, Inc.
C7200 platform with 1048576 Kbytes of main memory
Readonly ROMMON initialized
Self decompressing the image : ########################################################################### [OK]
% No interface specified for interface_command
% No interface specified for interface_command
% No interface specified for interface_command
% No interface specified for interface_command
% No interface specified for interface_command
% No interface specified for interface_command
% No interface specified for interface_command
% No interface specified for interface_command
% No interface specified for interface_command
% No interface specified for interface_command
% No interface specified for interface_command
% No interface specified for interface_command
% Cannot set multilink group. Interface Multilink2 does not exist
% Cannot set multilink group. Interface Multilink2 does not exist
% Cannot set multilink group. Interface Multilink2 does not exist
% Cannot set multilink group. Interface Multilink9 does not exist
% Cannot set multilink group. Interface Multilink9 does not exist
% Cannot set multilink group. Interface Multilink10 does not exist
% Cannot set multilink group. Interface Multilink10 does not exist
% Cannot set multilink group. Interface Multilink3 does not exist
% Cannot set multilink group. Interface Multilink3 does not exist
% Cannot set multilink group. Interface Multilink3 does not exist
% Cannot set multilink group. Interface Multilink3 does not exist
% Cannot set multilink group. Interface Multilink3 does not exist
% Cannot set multilink group. Interface Multilink3 does not exist
% Cannot set multilink group. Interface Multilink7 does not exist
% Cannot set multilink group. Interface Multilink7 does not exist
% Cannot set multilink group. Interface Multilink4 does not exist
% Cannot set multilink group. Interface Multilink4 does not exist
% Cannot set multilink group. Interface Multilink5 does not exist
% Cannot set multilink group. Interface Multilink5 does not exist
% Cannot set multilink group. Interface Multilink8 does not exist
% Cannot set multilink group. Interface Multilink8 does not exist
% Cannot set multilink group. Interface Multilink11 does not exist
% Cannot set multilink group. Interface Multilink11 does not exist
% Cannot set multilink group. Interface Multilink6 does not exist
% Cannot set multilink group. Interface Multilink6 does not exist
% Cannot set multilink group. Interface Multilink6 does not exist
% Cannot set multilink group. Interface Multilink12 does not exist
% Cannot set multilink group. Interface Multilink12 does not exist
Self decompressing the image : ###################################################################################################################################################################################################################################################### [OK]
Restricted Rights Legend
Use, duplication, or disclosure by the Government is
subject to restrictions as set forth in subparagraph
(c) of the Commercial Computer Software - Restricted
Rights clause at FAR sec. 52.227-19 and subparagraph
(c) (1) (ii) of the Rights in Technical Data and Computer
Software clause at DFARS sec. 252.227-7013.
cisco Systems, Inc.
170 West Tasman Drive
San Jose, California 95134-1706
Cisco IOS Software, 7200 Software (C7200-ADVIPSERVICESK9-M), Version 12.4(15)T7, RELEASE SOFTWARE (fc3)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2008 by Cisco Systems, Inc.
Compiled Thu 14-Aug-08 03:06 by prod_rel_team
Image text-base: 0x600089D8, data-base: 0x632911A0
This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.
A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
If you require further assistance please contact us by sending email to
[email protected].
Cisco 7206VXR (NPE-G1) processor (revision B) with 983040K/65536K bytes of memory.
Processor board ID 31651452
SB-1 CPU at 700MHz, Implementation 1025, Rev 0.2, 512KB L2 Cache
6 slot VXR midplane, Version 2.7
Last reset from power-on
PCI bus mb1 (Slots 1, 3 and 5) has a capacity of 600 bandwidth points.
Current configuration on bus mb1 has a total of 90 bandwidth points.
This configuration is within the PCI bus capacity and is supported.
PCI bus mb2 (Slots 2, 4 and 6) has a capacity of 600 bandwidth points.
Current configuration on bus mb2 has a total of 490 bandwidth points.
This configuration is within the PCI bus capacity and is supported.
Please refer to the following document "Cisco 7200 Series Port Adaptor
Hardware Configuration Guidelines" on Cisco.com <http://www.cisco.com>
for c7200 bandwidth points oversubscription and usage guidelines.
2 FastEthernet interfaces
3 Gigabit Ethernet interfaces
4 Channelized T1/PRI ports
2 Channelized T3 ports
509K bytes of NVRAM.
Installed image archive
250880K bytes of ATA PCMCIA card at slot 2 (Sector size 512 bytes).
16384K bytes of Flash internal SIMM (Sector size 256K).
Press RETURN to get started!
*Jun 7 01:21:56.191: %LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed state to up
*Jun 7 01:21:56.195: %LINEPROTO-5-UPDOWN: Line protocol on Interface VoIP-Null0, changed state to up
*Jun 7 01:21:56.195: %LINK-3-UPDOWN: Interface GigabitEthernet0/2, changed state to up
*Jun 7 01:21:56.195: %LINK-3-UPDOWN: Interface GigabitEthernet0/3, changed state to up
*Jun 7 01:21:56.199: %LINK-3-UPDOWN: Interface T3 1/0, changed state to down
*Jun 7 01:21:56.199: %LINK-3-UPDOWN: Interface T3 2/0, changed state to down
*Jun 7 01:21:56.199: %LINEPROTO-5-UPDOWN: Line protocol on Interface IPv6-mpls, changed state to up
*Jun 7 01:21:56.199: %LINK-3-UPDOWN: Interface FastEthernet4/0, changed state to down
*Jun 7 01:21:56.199: %LINK-3-UPDOWN: Interface FastEthernet4/1, changed state to down
*Jun 7 01:21:56.199: %ENVM-4-ENVWARN: NPE Inlet measured at 54C/129F
*Jun 7 01:21:56.207: %ENVM-4-ENVWARN: NPE Outlet measured at 54C/129F
*Jun 7 01:21:56.535: %SYS-6-CLOCKUPDATE: System clock has been updated from 01:21:56 UTC Mon Jun 7 2004 to 20:21:56 GMT Sun Jun 6 2004, configured from console by console.
*Jun 7 01:21:57.319: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed state to up
*Jun 7 01:21:57.319: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/2, changed state to down
*Jun 7 01:21:57.319: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/3, changed state to down
*Jun 7 01:21:57.319: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet4/0, changed state to down
*Jun 7 01:21:57.319: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet4/1, changed state to down
*Jun 7 01:21:57.851: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel3, changed state to down
*Jun 7 01:21:57.851: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel10, changed state to down
*Jun 7 01:21:57.851: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel11, changed state to down
*Jun 7 01:21:57.851: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel13, changed state to down
*Jun 7 01:21:57.851: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel20, changed state to down
*Jun 7 01:21:57.851: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel30, changed state to down
*Jun 7 01:21:57.851: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel40, changed state to down
*Jun 7 01:21:58.199: %LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed state to down
*Jun 7 01:21:58.451: %SYS-5-CONFIG_I: Configured from memory by console
*Jun 7 01:21:59.359: %SYS-5-RESTART: System restarted --
Cisco IOS Software, 7200 Software (C7200-ADVIPSERVICESK9-M), Version 12.4(15)T7, RELEASE SOFTWARE (fc3)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2008 by Cisco Systems, Inc.
Compiled Thu 14-Aug-08 03:06 by prod_rel_team
*Jun 7 01:21:59.399: %ENTITY_ALARM-6-INFO: ASSERT CRITICAL GBIC Slot 0/1 GBIC is missing
*Jun 7 01:21:59.399: %ENTITY_ALARM-6-INFO: ASSERT CRITICAL GBIC Slot 0/2 GBIC is missing
*Jun 7 01:21:59.399: %ENTITY_ALARM-6-INFO: ASSERT CRITICAL GBIC Slot 0/3 GBIC is missing
*Jun 7 01:21:59.619: %LINK-3-UPDOWN: Interface Serial1/0/1:0, changed state to down
*Jun 7 01:21:59.619: %LINK-3-UPDOWN: Interface Serial1/0/2:0, changed state to down
*Jun 7 01:21:59.619: %LINK-3-UPDOWN: Interface Serial1/0/3:0, changed state to down
*Jun 7 01:21:59.619: %LINK-3-UPDOWN: Interface Serial1/0/4:0, changed state to down
*Jun 7 01:21:59.619: %LINK-3-UPDOWN: Interface Serial1/0/7:0, changed state to down
*Jun 7 01:21:59.619: %LINK-3-UPDOWN: Interface Serial1/0/8:0, changed state to down
*Jun 7 01:21:59.619: %LINK-3-UPDOWN: Interface Serial1/0/9:0, changed state to down
*Jun 7 01:21:59.619: %LINK-3-UPDOWN: Interface Serial1/0/10:0, changed state to down
*Jun 7 01:21:59.619: %LINK-3-UPDOWN: Interface Serial1/0/11:0, changed state to down
*Jun 7 01:21:59.619: %LINK-3-UPDOWN: Interface Serial1/0/12:0, changed state to down
*Jun 7 01:21:59.619: %LINK-3-UPDOWN: Interface Serial1/0/14:0, changed state to down
*Jun 7 01:21:59.619: %LINK-3-UPDOWN: Interface Serial1/0/15:0, changed state to down
*Jun 7 01:21:59.619: %LINK-3-UPDOWN: Interface Serial1/0/16:0, changed state to down
*Jun 7 01:21:59.619: %LINK-3-UPDOWN: Interface Serial1/0/17:0, changed state to down
*Jun 7 01:21:59.619: %LINK-3-UPDOWN: Interface Serial1/0/18:0, changed state to down
*Jun 7 01:21:59.619: %LINK-3-UPDOWN: Interface Serial1/0/19:0, changed state to down
*Jun 7 01:21:59.619: %LINK-3-UPDOWN: Interface Serial1/0/20:0, changed state to down
*Jun 7 01:21:59.619: %LINK-3-UPDOWN: Interface Serial1/0/21:0, changed state to down
*Jun 7 01:21:59.619: %LINK-3-UPDOWN: Interface Serial1/0/23:0, changed state to down
al1/0/24:0, changed state to downOWN: Interface Seri
*Jun 7 01:21:59.619: %LINK-3-UPDOWN: Interface Serial1/0/25:0, changed state to down
*Jun 7 01:21:59.619: %LINK-3-UPDOWN: Interface Serial1/0/26:0, changed state to down
*Jun 7 01:21:59.619: %LINK-3-UPDOWN: Interface Serial1/0/27:0, changed state to down
*Jun 7 01:21:59.623: %LINK-3-UPDOWN: Interface Serial1/0/28:0, changed state to down
*Jun 7 01:21:59.623: %LINK-3-UPDOWN: Interface Serial2/0/1:0, changed state to down
*Jun 7 01:21:59.623: %LINK-3-UPDOWN: Interface Serial2/0/2:0, changed state to down
*Jun 7 01:21:59.623: %LINK-3-UPDOWN: Interface Serial2/0/4:0, changed state to down
*Jun 7 01:21:59.623: %LINK-3-UPDOWN: Interface Serial2/0/5:0, changed state to down
*Jun 7 01:21:59.623: %LINK-3-UPDOWN: Interface Serial2/0/6:0, changed state to down
*Jun 7 01:21:59.623: %LINK-3-UPDOWN: Interface Serial2/0/7:0, changed state to down
*Jun 7 01:21:59.623: %LINK-3-UPDOWN: Interface Serial2/0/8:0, changed state to down
*Jun 7 01:21:59.623: %LINK-3-UPDOWN: Interface Serial2/0/9:0, changed state to down
*Jun 7 01:21:59.623: %LINK-3-UPDOWN: Interface Serial2/0/10:0, changed state to down
*Jun 7 01:21:59.623: %LINK-3-UPDOWN: Interface Serial2/0/11:0, changed state to down
*Jun 7 01:21:59.623: %LINK-3-UPDOWN: Interface Serial2/0/12:0, changed state to down
*Jun 7 01:21:59.623: %LINK-3-UPDOWN: Interface Serial2/0/13:0, changed state to down
*Jun 7 01:21:59.623: %LINK-3-UPDOWN: Interface Serial2/0/14:0, changed state to down
*Jun 7 01:21:59.623: %LINK-3-UPDOWN: Interface Serial2/0/15:0, changed state to down
*Jun 7 01:21:59.623: %LINK-3-UPDOWN: Interface Serial2/0/16:0, changed state to down
*Jun 7 01:21:59.623: %LINK-3-UPDOWN: Interface Serial2/0/17:0, changed state to down
*Jun 7 01:21:59.623: %LINK-3-UPDOWN: Interface Serial2/0/18:0, changed state to down
*Jun 7 01:21:59.623: %LINK-3-UPDOWN: Interface Serial2/0/19:0, changed state to down
*Jun 7 01:21:59.623: %LINK-3-UPDOWN: Interface Serial2/0/20:0, changed state to down
*Jun 7 01:21:59.623: %LINK-3-UPDOWN: Interface Serial2/0/22:0, changed state to down
*Jun 7 01:21:59.623: %LINK-3-UPDOWN: Interface Serial2/0/24:0, changed state to down
*Jun 7 01:21:59.623: %LINK-3-UPDOWN: Interface Serial2/0/25:0, changed state to down
*Jun 7 01:21:59.623: %LINK-3-UPDOWN: Interface Serial2/0/26:0, changed state to down
*Jun 7 01:21:59.623: %LINK-3-UPDOWN: Interface Serial2/0/27:0, changed state to down
*Jun 7 01:21:59.623: %LINK-3-UPDOWN: Interface Serial2/0/28:0, changed state to down
*Jun 7 01:21:59.623: %LINK-3-UPDOWN: Interface Serial3/3:0, changed state to down
*Jun 7 01:21:59.631: %CRYPTO-6-ISAKMP_ON_OFF: ISAKMP is OFF
*Jun 7 01:21:59.631: %CRYPTO-6-GDOI_ON_OFF: GDOI is OFF
*Jun 7 01:21:59.663: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed state to down
*Jun 7 01:21:59.663: %LINEPROTO-5-UPDOWN: Line protocol on Interface NVI0, changed state to up
*Jun 7 01:21:59.695: %ENTITY_ALARM-6-INFO: ASSERT MAJOR T31/0 Physical Port Link Down
*Jun 7 01:21:59.695: %ENTITY_ALARM-6-INFO: ASSERT MAJOR T32/0 Physical Port Link Down
*Jun 7 01:21:59.695: %ENTITY_ALARM-6-INFO: ASSERT INFO Fa4/0 Physical Port Administrative State Down
*Jun 7 01:21:59.695: %ENTITY_ALARM-6-INFO: ASSERT INFO Fa4/1 Physical Port Administrative State Down
*Jun 7 01:21:59.695: %SNMP-5-COLDSTART: SNMP agent on host Core_7206_1 is undergoing a cold start
*Jun 7 01:22:00.239: %SYS-6-BOOTTIME: Time taken to reboot after reload = 318 seconds
*Jun 7 01:22:00.783: %LINK-3-UPDOWN: Interface GigabitEthernet0/2, changed state to down
*Jun 7 01:22:00.783: %LINK-3-UPDOWN: Interface GigabitEthernet0/3, changed state to down
*Jun 7 01:22:06.667: %ENTITY_ALARM-6-INFO: ASSERT MAJOR T31/0 Transmitter is sending remote alarm
*Jun 7 01:22:06.667: %ENTITY_ALARM-6-INFO: ASSERT MAJOR T31/0 Receiver has loss of signal
*Jun 7 01:22:07.915: %ENTITY_ALARM-6-INFO: ASSERT MAJOR T32/0 Transmitter is sending remote alarm
*Jun 7 01:22:07.915: %ENTITY_ALARM-6-INFO: ASSERT MAJOR T32/0 Receiver has loss of signal
Core_7206_1>
Core_7206_1>Those must be coming from the boot image, which doesn't have all the feature support as the regular IOS image. The messages are just warnings when configuring some of the features that the boot images doesn't understand.
-
Question on use of multi-mappings in interface mappings
We have the following scenario :
1. XI receives a orders05 idoc - xml and does a first message map - splitting this xml into two - a lookup key msg type and a copy of orders05 msg type ( 1:n )
2. These two messages from the first mapping are used in a second message mapping ( of type multi-mapping too ) ( n:1) to create the final orders05 message.
3. These two message maps are put sequentially in the interface mapping.
orders05 -> MessageMapping1 -> MessageMapping2 -> orders05 . Please note that our objective is to send one single ORDERS05 idoc into the end R3 system - using the idoc adapter. The use of multi-mapping is in the interim - and not in the idoc adapter.
Issues:
a. the "ns0:Messages" and "ns:Message[n]" tags are not being created automatically.
b. In the interface determination we do not see the interface mapping when we select the 'enhanced' option.
Any ideas, pointers as to what I am missing here ? I am on a critical timeline to implement this and can't understand whats going wrong ?Michal,
In your suggestion - to use two interface mappings - how I can configure the two interface mappings as a part of a single interface determination so that they execute one after the other . Or is it two interface determinations - one for each interface mapping - how do I relate these two ?
Also, I assume that since the message mappings in the interface mappings are multimappings , I need to use enhanced interface determination .
Could you share one of the scenarios wherein you had two interface mappings execute in a series - ? Thanks for your time. -
Prob with browser-based interface
hi
we have installed database server and application server on separate systems. MIS users/clients access the application by browser based interface. now, application server and database server are working properly. but when we wana access the application via browser the all the time there is an error that "the page cannot be displayed". anybody plz tell me to resolve this problem.
thanksThis sounds like the web server itself is down. I.e. the server platform is up and running, but the Apache web service is not running.
No idea what your environment consists of, but the typical way to start Oracle's Apache application server is
a) logon as the oracle o/s user on the web/application server platform
b) run the opmnctl (located at ORACLE_HOME/opmn/bin/opmnctl) to start the web server daemon
Note that this is a public forum staffed by volunteers. If you have a critical "system down" problem, you would be better served by filing a SR (Service Request) directly with Oracle Support via Metalink.
Maybe you are looking for
-
How do I select multiple albums in Revel to start/stop sharing?
How do I select multiple albums in Revel to start/stop sharing?
-
so the 3g has been out a while now and i still cant find an adapter so my CD player in my car will charge my iphone 3g. i see cablejive has made one that will be on sale soon, does anybody know if there is any other adapters already fro sale? http://
-
How to export tables on different condition
HI, i want to use export backup of my oracle 10g database, where i want to full export of some tables and some tables with "QUERY" parameter.so how can i make this script where some table are full exported and some based on condition. conditions defi
-
Hfs_swap_BTNode: offsets 31 and 32 out of order (0x0000, 0x0000)
I see this in the log when I have secure virtual memory turned on - does anyone know what this means?
-
After deleting dmg steam doesn't launch anymore
Hi guys, this is probably a dumb question (i've just moved to mac from a windows pc), so sorry if it is I downloaded the steam dmg provided by valve on their site, mounted it and moved the app to the applications folder, just like any other app insta