Microsoft Knowledge Base Email Alertz

(834479) - Describes an issue where you receive unexpected or unknown errors that refer to database files or to the RTC Server database.

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: 834479 - Last Review: August 2, 2005 - Revision: 4.2

You receive error messages when you run the Live Communications Server 2003 Setup program

On This Page

SYMPTOMS

When you run the Microsoft Office Live Communications Server 2003 Setup program to install a Live Communications Server 2003 home server, you receive an error message that is similar to one of the following:
Error 27780: Unknown error occurred while creating RTC Server database.
An unexpected error occurred while checking for necessary space for database files. Please try again.
Note You receive these error messages when you select the location to store the Live Communications Server 2003 database files, or when the Setup program tries to create the database files.

CAUSE

This issue occurs if the Microsoft SQL Server 2000 Desktop Engine (MSDE) installation does not register the Sqldmo.dll file correctly. This issue may occur if both of the following conditions are true:
  • You remove MSDE.
  • You run the Live Communications Server 2003 Setup program to install Live Communications Server 2003.

RESOLUTION

To resolve this issue, use one of the following methods, depending on whether MSDE is installed:

Method 1: Reinstall MSDE

If MSDE is not installed, reinstall it and then reinstall Live Communications Server 2003.

Method 2: Register Sqldmo.dll

If MSDE is installed, register the Sqldmo.dll file and then reinstall Live Communications Server 2003. To register the Sqldmo.dll file, follow these steps:
  1. Click Start, click Run, and then type regsvr32.exe sqldmo.dll.
  2. Click OK, and then click OK again.

Method 3: Make sure that %temp% has no spaces

Run the SET command at a command prompt. Make sure that both the TEMP variable and the TMP variable are set to 8.3 format. In 8.3 format, there are no spaces in the name. To change the TEMP variable to 8.3 format, run SET TEMP=C:\TEMP, where C:\TEMP is a folder that exists on the computer. To change the TMP variable to 8.3 format, run SET TMP=C:\TMP, where C:\TMP is a folder that exists on the computer.

MORE INFORMATION

The same error will occur if the Oledb32.dll is not the original release version of Microsoft Windows Server 2003. If you copy the correct version from another Windows Server 2003-based computer, the install will complete.

APPLIES TO
  • Microsoft Office Live Communications Server 2003
Keywords: 
kbprb KB834479
       

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

AndCycle - andcycle NOSPAM-AT-NOSPAM andcycle.idv.tw Report As Irrelevant  
Written: 2/9/2006 9:58 PM
there is another setting could result this error, the disk space check script depend on default share like \\computer name\c$ \\computer name\d$ blablabla, if you disable auto root share, the script will result this fail too, this problem took me 6hrs to find out.