Posted by beakersoft | Posted in Enterprise | Posted on 10-09-2007
Joy of joys, last week we had the auditors in, for 3 days no less. Now call me uneducated, but why would anyone want to do that job. One of them said to me (while looking for paperwork about a user account that never existed) that he ‘didn’t enjoy doing this’, problem was he had a big grin on his face when he said it. Hmmm, i’m sure he wasn’t lying at all.
The good thing was we had covered most of the things they wanted, so they started to get desperate (they aren’t doing there jobs if they cant find anything wrong). One of the ‘problems’ was apparently the windows on the server rooms were a security risk, we’re not sure why though. We found the best thing to do was to give them something small to get there teeth into and then leave them alone. The were chewing over ‘missing documentation’ for a small software version change for about 4 hours!
Because we knew they were coming, we tried to go round as many as the servers as we could and make sure they were fully service packed and patched. Just for a change, I managed to hit a couple of problems, this time it was with SQL reporting services not starting when I rebooted the server.
The first thing I noticed in the event log was a shed load of errors in the system log looking something like this:
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
to the user
I hunted the net, and this article solved this problem:
After a doing as suggested in this article, the DCOM errors stopped, but the SQL reporting service still wouldn’t start, all i was getting was the usual ‘did not respond in a timely fashion’ type of error in the system log.
So another search led me to this article:
Applying this reg key and rebooting then brought the service back to life. Reading more about this it seams that its just a timing issue. Why should applying a couple of patches cause a server without any problems to run its services up slower than it used to? Most of the things I found said this should only happen on slow servers, not after dodgy patches.