Jamik

Problem:
If you try to install SQL Server 2008 (without SP1) on a Windows 2008 R2 Server the setup fails with an application error.

Fix:
Install SP1 before starting the installation of SQL Server 2008. SP1 updates the required components which are used by the setup. Rerun SP1 after setup is finished.

References:

• http://support.microsoft.com/kb/955725

Problem (Event log entry):
The description for Event ID ( 0 ) in Source ( .NET Runtime ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Unable to open shim database version registry key - v2.0.50727.00000.

Fix:

• http://support.microsoft.com/kb/918642
• http://code.msdn.microsoft.com/KB918642

Problem:
If you try to load a MOSS/WSS page you get the javascript error

Error in loading dll
Line: 1935
Char: 4
Error: Error in loading DLL
Code:0

The exact line and character numbers can diver.

Description:
This error has to do with the presence integration in MOSS/WSS.

Fix:
Try a repair installation of your MS Office.

Problem:
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{61738644-F196-11D0-9953-00C04FD919C1} to the user DOMAIN\USERNAME SID (S-1-5-21-2949504220-1727672479-3499560203-1007).
This security permission can be modified using the Component Services administrative tool.

Fix:
Open COM administration and grant launch and activation permissions at the OSearch component to the specific service account.

Problem:
The application-specific permission settings do not grant Local Activation permission for
the COM Server application with CLSID {61738644-F196-11D0-9953-00C04FD919C1}  to the user
DOMAIN\USERNAME SID (S-1-5-21-2949504220-1727672479-3499560203-1007).
This security permission can be modified using the Component Services administrative tool.

Fix:
Open you COM administration and grant launch and activation permissions at the IIS WAMREG admin Service component to the specific service account.

After doing a fresh installation of MOSS 2007 on a single machine (developer box, no AD, no exchange) and trying to configure the “Office SharePoint Server Search” i stumbled upon the following error after trying to start the search service.

"An unhandled exception occurred in the user interface.Exception Information: OSearch (SERVICENAME)."

Reason:
I’ve accidently used only the “username” format without “domainname\” as service name.

Fix:
Use the “domainname\username” format.

Related:

• http://support.microsoft.com/kb/928620/en-us

Just installed BCB5 on one of my W2003 Developer Boxes and as usual the Data Execution Prevention results in Access Violations with a few Packages on BCB 5 (dclite50.bpl). So for further references – if you’re working with BCB 5 on Windows 2003 and getting AV’s – disable the Data Execution Prevention of Windows 2003.