|
Sharepoint Central Administration Launches with Firefox Instead of IE |
|
Written by Harry Zheng
|
|
After installing some updates for FireFox, the Sharepoint Central Administration started to launch with Firefox instead of IE. We all have seen similar behavior in other places where the browsers compete to be the default browser, so I checked the default browser setting for IE.

It appears that IE is the default browser. I even tried to set FireFox as default browser and then reset IE as default, but that didn't help either.
Thanks to this post, I found the fix. It appears the set as default browser action doesn't reset the shell class in this registry location:
HKEY_CLASSES_ROOT\http\shell\open\command

After set it to use IE, Sharepoint Central Administration launches in IE properly.

|
|
|
Project Server error in eventvwr |
|
Written by Harry Zheng
|
|
Error loading and running event receiver Microsoft.Office.Project.PWA.WSSEventReceivers.PSDBUpdater in Microsoft.Office.Project.Server.PWA,Version=12.0.0.0,Culture=neutral,PublicKeyToken=71e9bce111e9429c. Additional information is below.
: Unexpected end of file while parsing Name has occurred. Line 1, position 256.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
|
|
Project Server Timesheet error |
|
Written by Harry Zheng
|
|
"This timesheet is being processed by the system and is unavailable. The data shown above is that of the last successful save of the timesheet. Changes have been sent to the server and will process in the order received."
|
|
|
TFS build scheduler unstable? |
|
Written by Harry Zheng
|
|
I have scheduled a build to start every Thursday at 7:00PM. It didn't start last week. In fact I scheduled before Thursday and that should have given it enough time to start at 7:00PM.
So I manually started the build and thought it would then reschedule the next build to this Thursday. Surprised I received an email telling me the build was successful as of last night (Tuesday). Now if it behavours like this, how can I trust it will do the job on Thursday or not. |
|
Project Server database autoclose |
|
Written by Admin
|
|
If you install Office Project Server with all the default options, you will most likely end up with an SQL Server 2005 Express edition at the back end. These Project Server databases have AutoClose option set to True by default, and it can generate a lot of error messages in the event log. Basically the error messages point out that the specified databases were not readly available, or responding in a timely fasion, when Project Server tried to connect.
To get rid of these error messages, simply change the AutoClose option to False from SSMS.
And better than that, you can import Microsoft Best Practice policies and run the check AutoClose policy against all your Project Server databases. You will need to have access to at least one SQL Server 2008 instance to run the policy. |
|
Last Updated on Sunday, 04 October 2009 11:06 |
|
|
|
|
|
|
Page 1 of 2 |