Recording Service Fails After Installing Security Update for Windows XP (KB925902)

[davidl]

Yesterday I installed the Security Update for Windows XP (KB925902) and rebooted. After that the recording service would not run at all. It would not start automatically after a reboot and would not start when I started the UI. I did get one windows error and here is the entry in the application events in the event viewer:

Event Type: Error
Event Source: .NET Runtime 2.0 Error Reporting
Event Category: None
Event ID: 5000
Date: 4/4/2007
Time: 7:10:32 AM
User: N/A
Computer: MAIN
Description:
EventType clr20r3, P1 gbpvr.exe, P2 1.0.2614.27229, P3 5, P4 system.data.sqlite, P5 1.0.30.1, P6 44a7e70d, P7 11f, P8 2e, P9 system.data.sqlite.sqlite, P10 NIL.

The solution to this problem was to run the GVPVR 99.12 installer and select the repair option. After this everything is working correctly again.

[sub]

I installed KB925902 this morning and it seems to still be running fine here, but zip and attach your logs and I'll see if I can see any other cause.

[sub]

Did you look into this hot fix: http://support.microsoft.com/kb/935448/

It address an issue some people have had with KB925902

[rowle1jt]

Also note that it can affect RealTek HD audio cards... could this have also contributed to your issue?

[davidl]

Thanks for offering these suggestions. Both of you are very helpful!

I looked at the 935448 hot fix and while I do have Realtek audio, specifically Realtek AC'97, I did not see any of the specific symptoms mentioned.

My logfiles are attached.

[sub]

Can you reset your logging level to the default 'debug' level, then reproduce and repost the logs.

[davidl]

Sorry I have not responded in a while as I have been out of town. I have changed the logging level to debug, but I am not sure how to reproduce the logs. The error has not recurred since I ran the installer and used the repair option.

[sub]

I have changed the logging level to debug, but I am not sure how to reproduce the logs.

They're always produced. See the logs directory.

The error has not recurred since I ran the installer and used the repair option.

Ok, dont bother posting the logs then.