SMS Site problems

[drewdown]

Today my SMS site started acting up, not sure if its because my coworker was patching it or what. However, scripts that run on every machine upon login started to fail on teh SMS box.

From the SMS client access point, component server, management point, SMS reporting point and the Site server. All showing this error message.

The component raised an exception but failed to handle it and will be stopped immediately.

Component name: SMS_SQL_MONITOR
Executable: C:\SMS\bin\i386\smsdbmon.exe
Process ID: 3948
Thread ID: 4864
Instruction address: 7768F202
Exception code: C0000005 (EXCEPTION_ACCESS_VIOLATION)
Additional information: The thread tried to read from the virtual address 00000060 for which it does not have the appropriate access

Any idea what is going on?

 

[drewdown]

I see this in the smsdbom.log files, repeated a fair amount of times:

Waiting for SMS_INBOX_MANAGER to create the "Status Manager" inbox. Sleeping for 60 seconds. The operating system reported error 64: The specified network name is no longer available. SMS_SQL_MONITOR 6/27/2006 4:52:21 PM 6096 (0x17D0)
WARNING: Still waiting for SMS_INBOX_MANAGER to create the "Status Manager" inbox. Sleeping for 60 seconds. The operating system reported error 64: The specified network name is no longer available. SMS_SQL_MONITOR 6/27/2006 4:57:22 PM 6096 (0x17D0)
ERROR: Still waiting for SMS_INBOX_MANAGER to create the "Status Manager" inbox. Sleeping for 60 seconds. The operating system reported error 64: The specified network name is no longer available. SMS_SQL_MONITOR 6/27/2006 5:02:22 PM 6096 (0x17D0)

 

[tbrennans]

there was one of the patches released ms06-025 that screwed up dailup scripts from running but I had not heard about other things it might have hosed....

I'd reboot and see if that fixes it, at the end of this is a ms case number, you can call and see if it would be an issue in this case also.

We have received some reports of a potential issue with MS06-025. Here is a snippet of what appears to be the problem as it was report to us:

"We received couple of calls that users are
not able to dial up after applying MS06-025 (KB911280).

I verified this on a test machine and it looks like it breaks dial up.

We have some scripts that need to be run in order to authenticate the user
properly after the dial up connection is established.

It looks like the patch prevents scripts from running at all. Even when I
turned on the terminal window (in interactive logon and scripting) I can't
log in manually at all. After the connection is established I can see the
Username prompt in the terminal window but I can't enter any data.

Uninstalling the patch fixes this."


Microsoft has confirmed they are getting some reports of this and have established a case number. If you are having similar problems, call Microsoft for free support, 1-(866) PC-SAFETY, and reference case number SOX060615700008.

SANS - Internet Storm Center - Cooperative Cyber Threat Monitor And Alert System.

 

[drewdown]

Scripts arent running on it anymore, we have a script that maps network drives and it is not running on our SMS server. Nor do I see an unistall for that update, which I believe to be KB911280.

I am calling Microsoft now.

 

[tbrennans]

you can uninstall from the %win%\$NTUninstallKB911280$\spuninst\spunist.exe file :-D

 

[drewdown]

Its not there, the machine was acting strange and my fellow admin told me he was patching it. He attempted to kill the updates but they hung so I had to reboot the machine, now its fubar'd.

Also, I cannot path out to our SMS site, but I can RD into it and path out to other servers from it.

 

[drewdown]

Also seeing this in the inboxmgr.log file:

"Path 'MSWNET:["SMS_SITE=FFX"]\\*********\CAP_FFX\' is inaccessible

 

[tbrennans]

ooooh sounds ugly. You have a backup from before the patch attempt?

I would try to install those patches again, then remove 025.. it just sounds like a beginning of a bad time to me!

I'm not feeling all warm and fuzzy about giving any advice one way or another in this situation if you know what i mean.

Tim B

 

[drewdown]

Dodged a bullet on this one. Re-applied the updates and everything went back to normal. I suspect the updates hung and in the process screwed up networking on the server, wouldnt allot me to change the computer, name, path out to it, run any scripts, just plain weird stuff.

Everything is working fine now though.

Thanks a lot Tim.

 

[tbrennans]

Glad it worked out that way for you!!