Spooler service stops

The case of the mysterious stopping spooler has been solved. At least this time.

Good old Microsoft. You send in errors, look up errors and can not find anything from Microsoft itself. Half the time the people in the Technet Forums treat people with almost a snark to them, and don’t listen. Canned answers, no answers, and worst of all no information.

I recently had one of those spooler.exe keeps stopping problems. Went through all the logs, did my Internet searches and came up with an answer. c:\windows\system32\spooler\print needed to be cleaned out. Simple answer, which I found archived from a forum question about 4 years ago. Not an official Microsoft forums mind you, just a general IT forum.I find more things away from Microsoft than on their site.

It is frustrating. I am sure all of you have run into something similar. You look in the event logs and there is the “Click here for more information” link in the error message. Of course 99% of the time when you click on that link, the more information is sorry, we have no information on that error. The rest of the time it is just a general description that already has been stated inside the log entry.

Why does Microsoft tease us so? They have the perfect mechanism to help us, the ones who support their products, and yet they shun us. Yes there is a lot of other information out on the net, but sometimes you run into errors that you can’t find anyone else who has solved the error. Sometimes you want that information from Microsoft, without having to call them up and use an incident or pay for an incident. Last time I called up Microsoft, I had the problem figured out while on hold because the Microsoft Technician was asking for help. He couldn’t find information on the error codes.

Microsoft wants to be a big name in search. They have the perfect mechanism to help take Google down a peg with the links in the error log entries. Why they don’t get that working properly, I have no clue.

Monday Microsoft Musings

Monday morning, another work week starting, and a bunch of thoughts and questions about Microsoft for you all.

First off, how does Microsoft determine when it is going to release new software? SBS 2008, which has Exchange 2007 built in it, just came out in November, and now Exchange 2010 is in beta. How fast do they expect people to change? Figuring that it take a while for companies to even consider switching to the newest software, and then the testing and learning curve for it, maybe there is a method to the fast turn around on the next gen software.

Second, and even more annoying to me, is the links inside of the Microsoft Event Logs.   You click on the link, it asks you if you want to send the information, and then 80-90 percent of the time you get a message back saying there is no information from Microsoft on this Event ID. Why the heck do they even offer us a link when most of the time it does nothing but make us bang our heads? Yes there are great ways of finding out about the Event IDs through Google, but the links inside of the event logs are supposed to make our search much easier, and more official.

So, am I way off base on these thoughts? Am I just another looney IT guy who wants more from his vendors than they give, or do you feel the same way?

More on XP and other End of Cycles software

So, while mainstream support is ending for Windows XP, it seems that Microsoft is going to continue to allow downgrades by manufacturers until sometime next year. Yeah, this is both good and bad, especially considering that warranty support ends on Tuesday, April 14. Are the PC makers going to do warranty support for XP still is the big question. I would love to say yes, but who knows.

Also on the XP front, You will be able to downgrade from the upcoming Windows 7 to XP.  This does by companies some time to upgrade, but how long?

Tuesday, April 14 also marks the end of mainstream support for Office 2003. Same rules apply as with XP.

Now on July 14 of this year Office 2000 is dead to Microsoft. No more security updates, no support, nothing. Same thing happens to Windows 200 on July 13, 2010. Time to start planning accordingly, especially for Office 2000. Make sure you try to get your clients off of it before then for a smooth transition.