I will give Microsoft credit, they figured out they were going in the wrong direction, better late then never i guess. Being successful these days is difficult and really requires sticking to your strength’s. Microsoft has accepted that they need a return to their fundamentals, ripping off other people’s ideas and stop trying to have original ones of their own. I foresee a bright future for Windows 7.]]>
I think this is pretty straightforward idea that when you produce a product you should want people to be able to fix the product as easily as possible. Obstacles and challenges in the movies are great but finding a bug fix on a vendor site should not warrant difficulties worthy of the next Indiana Jones flick. I am going to quote a unnamed vendor rep who once told me in response to a question about getting better info about their product in their knowledgebase “It doesn’t look good for us if we post all of these issues”, to which I responded “I understand, however it looks even worse when we waste 10 hours trying to fix a problem only to call your tech support line and find out that it is a known issue with a easy work around”.
I would like a make a specific mention of Blackberry’s knowledgebase (http://www.blackberry.com/btsc/). I have used this knowledgebase on several occasions and found that it was excellent. This is the example by which all other vendor knowledebase’s should be judged.]]>
I eventually resolved the issue by running handheldcleanup -u command. This exectuable is located in the utility folder of the Blackberry installation folder (C:\program files\research in motion\blackberry enterprise server\utility\handheldcleanup.exe). This command cleans up the BES database of any old data needing to be purged.]]>
Fast forward to today and we are beginning to see the same thing all over again. Xerox announced today that they are cutting 3000 staff. Anyone with any level of foresight could tell you that HP is eyeing EDS like a fatty roast to trim. This is just the beginning though, there is much more of this to com. From my experience when things get tight at a company this first thing that gets cut is IT.
Hopefully things get sorted out quickly because I for one have no desire to wax nostalgic in the unemployment line.]]>
You still need the robocopy executable (which you need to specify the location of in the app), but this takes care of all the hassle of the commandline switches.
Check it out!]]>
“An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 – Error Locating Server/Instance Specified)”
The soltuon? SQLServeragent service wasn’t running. Not a difficult problem in the scheme of things but is it too much to ask of software vendors to program in error messages that actually point you in the right direction?
How hard would it be to provide an error message like “The SQLserver agent service currently is running. Please go into the services MMC in order to enable it”. Would that make people’s lives to simple?]]>