Folks, some members of my team are having a problem installing a LGR for a lab setup. Specifically, after completing an NT and SQL 7 install, the box works just fine. After installing the LGR software, the box just spins like a top...continuous reboot after the NT login splash screen.
We're working to build another partition on the HDD with a clean NT install and nothing else, so that we can view the NT logs to see what they may say, but it's slow going (they are RAID drives, and pulling the RAID drivers for a DOS boot to add a partition is proving to be very challenging).
No ICM services are configured as auto-start on that box. The server's Server Tools partition is intact.
We've also tried installing the RTR, with the same results.
(We never tried it on a Dell). If during the install of ICM (during the file copy) you got a weird setup error message then this has been, for us at least, the indicator the CDP did not install properly. A reboot after this will cause the problem you described.
The CDP issue is caused by the the NIC Bindings not being set in registry correctly during the initial Service Pack 0 installation. I was told it only occurs on 'multi homed' boxes, but that is not true - even single NIC machines like Network AWs are effected.
Cisco have told me this will not be fixed in ICM 4.5 ie. 4.5a will not help. ICM 4.6 will be OK.
A work-around exists:
1. After the ICM upgrade / install and hotfixes are applied and BEFORE the reboot go to C:\winnt\system32\etc\drivers directory and rename the CDP.SYS file to CDP.SYS.OLD
I've been working on this particular issue on an ICM 4.5 deployment in the past month. Just wanted to take a quick moment and thank everyone for their input, Tim P-M for submitting this for me and especially Roy Nelson for the solution. I followed your suggested instructions and it solved the problem immediately. Any ideas what specifically causes this? I'm sure it's not multi-homed machines also. I've experienced this problem on both Dell PowerEdge and HP LC servers. One had a single NIC and one had dual.
The only thing I can see in common is both servers had integrated NICs. I'm not sure of the chipset, I didn't investigate that far once the problem was solved. Maybe the issue is specific to a particular chipset?
Personally, I don't plan on spending too much time narrowing this down if the issue is resolved in 4.6. However, for curiosity's sake...any thoughts are welcomed.
I'm not able to access my old voice mail messages all of a sudden. The recording says something like 'the message is currently not available'. This has never happened before in all the years I have been using this system. I have t...