Microsoft Knowledge Base Email Alertz
All KB/RSS Links  |  Hot Kb!  |  New Kb!  |  Scott Cate  |  FAQ / KB  |  Web Hosting  |  Unsubscribe  

(832814) - When you install Microsoft Office SharePoint Portal Server 2003 with Microsoft SQL Server, and you try to create the configuration database, you receive the following error message: Error accessing database. Verify that the database server name and...

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.
Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks
Article ID: 832814 - Last Review: February 21, 2007 - Revision: 1.7

You receive an "Error accessing database" error message and other error messages when you try to create a SharePoint Portal Server 2003 or a Windows SharePoint Services configuration database

View products that this article applies to.

SYMPTOMS

When you install Microsoft Office SharePoint Portal Server 2003 or Microsoft Windows SharePoint Services with Microsoft SQL Server, and you try to create the configuration database, you receive the following error message:
Error accessing database. Verify that the database server name and the instance name (if present) are correct. Also, ensure the configuration database administration account has sufficient permissions on the server or instance and the service corresponding to your SQL Server instance is running.
When this issue occurs, the database is created but does not function. If you continue after you receive this error message, and you try to create a Portal, you receive the following error message:
Portal creation failed. Please see the portal creation log for more details.
The following error may also be recorded in the Portal log file:
10:29:54 Portal creation job exception. (status=PortalAdminJobStatusFailed) Microsoft.SharePoint.SPException: Must declare the variable '@SiteId'. (Error code: 137). ---> System.Runtime.InteropServices.COMException (0x81071717): Must declare the variable '@SiteId'. (Error code: 137).
If you are installing Microsoft Windows SharePoint Services, and you try to extend a virtual server, you receive the following error message:
Must declare the variable '@SiteId'. (Error code: 137).
Back to the top

CAUSE

This issue may occur if the SQL Server is configured to use case sensitive collation. SharePoint Portal Server 2003 requires that the collation name for the database be Latin1_General_CI_AS_KS_WS. This name most closely matches the Microsoft Windows NTFS file system collation.
Back to the top

RESOLUTION

To resolve this issue, use case-insensitive collation in SQL Server. The collation for SQL Server 2000 is configured when SQL Server is installed. To resolve this issue, remove, and then reinstall SQL Server with case-insensitive collation.
Back to the top

MORE INFORMATION

For information about how to install SQL Server with case-insensitive collation, follow the instructions in your SQL Server documentation.

For additional information about a related issue, click the following article number to view the article in the Microsoft Knowledge Base:
306492  (http://kbalertz.com/Feedback.aspx?kbNumber=306492/ ) STS: Error message: Unable to prepare tables in database...
Back to the top
APPLIES TO
  • Microsoft Office SharePoint Portal Server 2003
  • Microsoft Windows SharePoint Services 2.0
Back to the top
Keywords: 
kbdatabase kbuninstall kbsetup kberrmsg kbprb KB832814
Back to the top
        

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate

Kaushal - kaushi2 NOSPAM-AT-NOSPAM hotmail.com Report As Irrelevant  
Written: 8/29/2006 2:19 AM
Unfortunately, SQL Server 7.0 doesn't provide a mechanism for changing collations on the fly. To change the collation of an existing database, you need to rebuild the master database or reinstall SQL Server. You can find information about the rebuild process in SQL Server Books Online (BOL) in "How to rebuild the master database (Rebuild Master utility)." Remember, rebuilding the master database means re-creating all logins. And in SQL Server 7.0, you can't reattach a database that has a different collation than the server. You'll need to use another mechanism, such as Data Transformation Services (DTS) or bulk copy program (BCP), to bring the data back in. The process isn't much different than starting from scratch with a complete reinstall. Keep in mind that SQL Server 2000 has more flexibility for managing collations. You can change the default collation of a database after it's been installed and change or set collations at the column level for existing tables. If you've been thinking about upgrading to SQL Server 2000, collation flexibility might be the final reason to take the plunge. Note that changing the default collation of a database in SQL Server 2000 defines the collation of newly created objects but doesn't automatically change the collations of existing objects. You need to use the ALTER TABLE command to change the collation of an existing column. You can't change the collation of an entire table with one command, but you can change the collation for all columns within the table.



Copyright © 2002-2007 KBALERTZ.COM.  All Rights Reserved. Terms / Privacy. Discount ASP.NET Hosting