| Message ID | Severity | Message |
|---|---|---|
|
1300 |
Informational |
Network Discovery is starting. |
|
1301 |
Informational |
Network Discovery is retrieving information about previously discovered devices and networks from CIM Object Manager. This process can take a long time when many devices are being discovered. |
|
1302 |
Informational |
Network Discovery protocol modules are initializing. |
|
1303 |
Informational |
Network Discovery is starting protocol operations. Network Discovery is querying network devices to discover devices related to the specified configuration. |
|
1304 |
Informational |
Network Discovery is stopping protocol operations. |
|
1305 |
Informational |
Network Discovery is stopping the Network Discovery protocol modules. |
|
1306 |
Informational |
Network Discovery is storing currently discovered devices and networks in CIM Object Manager, which can take a long time when many devices are being discovered. |
|
1307 |
Informational |
Network Discovery is exporting devices and networks to the Discovery Data Manager. This process can take a long time when many devices are being discovered. |
|
1308 |
Informational |
Network Discovery has stopped. |
|
1309 |
Error |
Network Discovery failed to connect to a DHCP server due to insufficient access. This error message means that fewer clients and networks will be found than otherwise. Note that this message will not be generated again during this Network Discovery session, regardless of how often the error occurs. Possible cause: the DHCP server is running in a domain in which the SMS Service account is not available. (Network Discovery runs under the SMS Service account as part of SMS Executive.) Solution: Create an account on the DHCP server’s domain with the same name and password as the SMS Service account. |
|
1310 |
Error |
Network Discovery failed to connect to a DHCP server due to a connection error. (Network Discovery can communicate only with Microsoft DHCP servers; if you do not use these servers, you can ignore this error.) Solution: If you are using Microsoft DHCP servers, then refer to the specific error string for details. This error message means that fewer clients and networks will be found than otherwise. Note that this message will not be generated again during this Network Discovery session, regardless of how often the error occurs. |
|
1311 |
Error |
Network Discovery failed to perform a WinSock operation. Solution: Ensure that the TCP/IP stack is installed and running. Also, verify that you are using Windows NT version 4.0 or later. This error message means that fewer clients and networks will be found than otherwise. Note that this message will not be generated again during this Network Discovery session, regardless of how often the error occurs. |
|
1312 |
Warning |
Network Discovery failed to perform a WinSock operation relating to multicast membership. Network Discovery will not discover other routers on your local subnet by listening for OSPF packets. However, if Network Discovery can detect your default gateway using SNMP, it will find those routers anyway. Possible cause: Some other network software on the server is preventing Network Discovery from joining the OSPF multicast group. Solution: Ensure that the TCP/IP stack is installed and running. Also, verify that you are using Windows NT version 4.0 or later. Note that this message will not be generated again during this Network Discovery session, regardless of how often the error occurs. |
|
1313 |
Warning |
Network Discovery did not have time to finish. Therefore, the information in the SMS site database is not as complete as it should be. Solution: Increase the duration of the discovery. In the Network Discovery Properties dialog box, on the Schedule tab, select a schedule and open the Schedule dialog box. Note that the duration of the discovery is the amount of time spent performing protocol transactions, not the overall time Network Discovery performs processing. |
|
1314 |
Error |
Network Discovery failed to connect to CIM Object Manager. Network Discovery cannot continue because all its configuration information is retrieved from CIM Object Manager. Possible cause: CIM Object Manager is not installed on this computer. Solution: Install CIM Object Manager by running Sms\Bin\[i386|Alpha]\Wbemsdk.exe. |
|
1315 |
Error |
Network Discovery detected CIM Object Manager, but could not establish a connection to it. Network Discovery cannot continue because all its configuration information is retrieved from CIM Object Manager. Possible cause: This computer has an incompatible version of CIM Object Manager, or there was an internal error within CIM Object Manager. Solution: Reinstall CIM Object Manager by running Sms\Bin\[i386|Alpha]\Wbemsdk.exe. |
|
1316 |
Error |
Network Discovery failed to read information from CIM Object Manager. Network Discovery cannot continue. Possible cause: The Network Discovery MOF file is not loaded. Solution: Load the MOF file by running “Winnt\System32\Wbem\Mofcomp.exe NetDisc.MOF”. Possible cause: There was an internal error within CIM Object Manager. Solution: Reinstall CIM Object Manager by running Sms\Bin\[i386|Alpha]\Wbemsdk.exe. |
|
1317 |
Warning |
Network Discovery failed to read information from CIM Object Manager. Network Discovery will continue, but slowly. Possible cause: The Network Discovery MOF file is not loaded. Solution: Load the MOF file by running “Winnt\System32\Wbem\Mofcomp.exe NetDisc.MOF”. Possible cause: There was an internal error within CIM Object Manager. Solution: Reinstall CIM Object Manager by running Sms\Bin\[i386|Alpha]\Wbemsdk.exe. |
|
1318 |
Error |
Network Discovery failed to write information to CIM Object Manager. Network Discovery cannot continue. Possible cause: The Network Discovery MOF file is not loaded. Solution: Load the MOF file by running “Winnt\System32\Wbem\Mofcomp.exe NetDisc.MOF”. Possible cause: There was an internal error within CIM Object Manager. Solution: Reinstall CIM Object Manager by running Sms\Bin\[i386|Alpha]\Wbemsdk.exe. |
|
1319 |
Warning |
Network Discovery failed to write information to CIM Object Manager. Network Discovery will continue, but slowly. Possible cause: The Network Discovery MOF file is not loaded. Solution: Load the MOF file by running “Winnt\System32\Wbem\Mofcomp.exe NetDisc.MOF”. Possible cause: There was an internal error within CIM Object Manager. Solution: Reinstall CIM Object Manager by running Sms\Bin\[i386|Alpha]\Wbemsdk.exe. |
|
1320 |
Warning |
Network Discovery failed to execute a query from CIM Object Manager. Network Discovery will continue, but slowly. Possible cause: The Network Discovery MOF file is not loaded. Solution: Load the MOF file by running Winnt\System32\Wbem\mofcomp.exe NetDisc.MOF. Possible cause: There was an internal error within CIM Object Manager. Solution: Reinstall CIM Object Manager by running Sms\Bin\[i386|Alpha]\Wbemsdk.exe. |
|
1321 |
Error |
Network Discovery failed to communicate with some SNMP devices because of an internal problem with SNMP resources. Network Discovery will continue, but slowly. The discovery duration might have to elapse before discovery can finish fully. Possible cause: Too many SNMP-related applications are running on this computer. Solution: Close some SNMP-related applications. Possible cause: An internal error. Solution: Re-run Network Discovery. If that does not work, reboot. If that does not work, contact your network administrator. |
|
1322 |
Error |
Network Discovery failed to export a device to the Discovery Data Manager. Therefore, discovered devices will not appear in the SMS site database. Possible cause: There is not enough free disk space on the SMS site server. Solution: Free some disk space and re-run Network Discovery. |
|
1323 |
Error |
Network Discovery failed to export a network to the Discovery Data Manager. Therefore, discovered devices will not appear in the SMS site database. Possible cause: There is not enough free disk space on the SMS site server. Solution: Free some disk space and re-run Network Discovery. |
|
1324 |
Informational |
Network Discovery failed to enumerate the computers on one or more domains. Possible cause: The specified domains do not exist. Solution: Re-specify domains; go to the Network Discovery Properties dialog box, Domains tab. Possible cause: Domain access problems exist. Solution: Contact your network administrator. |