OAM service hangs after SCCS site name change

[picklemogg]

Anyone have any ideas on this one? We have recently updated the SCCS site name. For the first day or so everything seemed fine. The second day we noticed a problem with accessing user/agent information. Basically hour glasses when trying to pull up info. All call processing/data collection seems fine. Looks like this is pointing to the OAM service. I think that it has something to do with old "classic client" scheduled reports running without the updated site name in conjunction with web client. If we reboot web client, the OAM service clears and life is good. Thanks in advance.

 

[TheWorkingMan]

Does your Web Client Server have two NICs?

 

[picklemogg]

Yes, two NIC cards. We've actually had the Web Client Server online for about 6 months now. Haven't really had many problems with the Web Server at all. Once we changed the site name on the SCCS, the Web Server seemed to have caused the OAM service to shutdown. Since we restarted the web server a few days back, the OAM service has been fine. Will the service eventually shutdown again or did restarting the Web Server solve the problem once and for all? I still feel that it may have something to do with web client server being connected to SCCS and also shceduled reports running from classic with the old site name referenced (we did delete all old reports from the scheduler).

I guess it could be coincidental, but this actually happened to me at two different sites...different SCCSs and Web Servers. Changed the site name and boom 12 hours later OAM shutdown at both sites. Restarted Web Server and have been in business since?

Any further thoughts would be appreciated. Thanks.

 

[TheWorkingMan]

You will need to disable APIPA on the web server. Using Regedit do the following:

Under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

Add the following value to this key:
Value Name: IPAutoconfigurationEnabled
Value type: REG_DWORD
Value in hexadecimal: 0 (value of 0 disables APIPA)

After making this change reboot the web server.

This will prevent the OAM timeout.

Reference Nortel Bulletin 2003_0266

TWM