Could not create SSOSQL. Error Code: 0x80131700

This is for x64 OS:

"C:\Windows\Microsoft.NET\Framework\v2.0.50727\regasm.exe" "C:\Program Files\Common Files\Enterprise Single Sign-On\win32\ssosql.dll"

"C:\Windows\Microsoft.NET\Framework64\v2.0.50727\regasm.exe" "C:\Program Files\Common Files\Enterprise Single Sign-On\win32\ssosql.dll"

"C:\Windows\Microsoft.NET\Framework\v2.0.50727\regasm.exe" "C:\Program Files\Common Files\Enterprise Single Sign-On\ssosql.dll"

"C:\Windows\Microsoft.NET\Framework64\v2.0.50727\regasm.exe" "C:\Program Files\Common Files\Enterprise Single Sign-On\ssosql.dll"

Restoring SQL Server 2005 Suspect Database

Post from: http://mshehadeh.blogspot.com/2007/09/restoring-sql-server-2005-suspect.html

EXEC sp_resetstatus 'DBname'

ALTER DATABASE "DBname" SET EMERGENCY

DBCC checkdb('DBname')

ALTER DATABASE "DBname" SET SINGLE_USER WITH ROLLBACK IMMEDIATE

DBCC CheckDB ('DBname', REPAIR_ALLOW_DATA_LOSS)

ALTER DATABASE "DBname" SET MULTI_USER

The SSO service failed to start. After installing VS 2010

Post from: http://blogs.msdn.com/ashishme/archive/2009/08/14/fixing-biztalk-entsso-failure-on-windows-7-vista-or-server-2008-after-vs-2010-beta-installation.aspx\

I've been running BizTalk 2009 on my Windows 7 machine, and after installing VS 2010 beta 2, the Enterprise Single Sign-On Service stopped working.

It failed with the following error:

Could not create SSOSQL. To fix the problem, reinstall SSO or try 'regasm SSOSQL.dll' from a Visual Studio command prompt.
Error Code: 0x80131700

The file is located at C:\Program Files\Common Files\Enterprise Single Sign-On\SSOSQL.dll

Run Visual Studio Commmand prompt as Administrator and run 'regasm "C:\Program Files\Common Files\Enterprise Single Sign-On\SSOSQL.dll"'.

On 64 bit machines (windows 7, Vista, W2008 etc) you need to call regasm.exe utility explicitly from this folder:

C:\Windows\Microsoft.NET\Framework64\v2.0.50727\regasm.exe

The 'Microsoft.ACE.OLEDB.12.0' provider is not registered error with 64bit OS

Post from: http://weblogs.asp.net/cazzu/archive/2007/11/16/the-microsoft-ace-oledb-12-0-provider-is-not-registered-error-with-vista-64bit.aspx

If you're getting this error while trying to connect to Access 2007 or Excel 2007 via the Office 12 OleDB provider, you must first make sure you have the Office 2007 data providers installed.

Next, under x64 (64bit), the data providers will not work by default as they are 32-bit only (x86), even if the data providers download page doesn't say it. You have to explicitly compile for x86 instead of the default "Any CPU" platform:...

Read full article

The description for Event ID ( 17137 ) in Source ( MSSQL$MICROSOFT##SSEE ) cannot be found

Post from: http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.sharepoint.setup_and_administration&tid=71af2356-f92e-4b15-8b09-798a91288cc3&cat=〈=&cr=&sloc=&p=1

Solution:

Open SQL server management studio.

Right click the database and select Properties->Options.
See if Auto close is set to True. If it is true, set it to false.

The evaluation version of Microsoft Office SharePoint Server 2007 for this server has expired

http://support.microsoft.com/kb/971620

No exact match was found domain users. Domain users

Post from: http://weblogs.asp.net/erobillard/archive/2007/07/06/how-to-change-service-accounts-and-their-passwords-in-moss-and-wss-3-0.aspx

Change the Application Pool Identity for SharePoint Central Administration (SCA)

Repeat these steps on each server which hosts the SharePoint Central Administration web application. If the web front-end (WFE) and application (APP) server roles are served by separate machines, SCA should be enabled on one APP server (or more) and stopped and/or removed from the WFE servers. This allows control over access to the SCA. The SCA service account should not be the same as that used for the SharePoint application pool so even if one is compromised, the other remains secure.

1. Open a command prompt.
2. Run: stsadm -o updatefarmcredentials -userlogin domain\username -password password
3. Be patient. This may take a few minutes to run.
4. To restart the application pool, either open IIS and recycle the application pool, or open a command prompt and type iisreset -noforce
5. Open SharePoint Central Administration in a browser to confirm that the change was successful.

The above steps create an Administration Application Pool Credential Deployment timer job. You can see this in the Timer Job Definitions page. The job is complete when it no longer appears in the list of definitions (refresh the browser, this isn't automatic).