Lync 2010 - Publishing Topology error

Hi,

the first time I tryed to publish my topology I get the following error:

DbOwner is now sa
 IWGLAB2\RTCUniversalConfigReplicator is not a valid SQL login. A SQL login with this name will be created.
IWGLAB2\RTCUniversalConfigReplicator has a Win32_Account instance of SIDType 2
Global.SqlDmo.Logins.Add failed for IWGLAB2\RTCUniversalConfigReplicator

---------------
Exit code: ERROR_INVALID_ACCOUNT (-20)
---------------

Now, if I try to re-publish the topology I get:

Running script: C:\Windows\system32\cscript.exe //Nologo "C:\Program Files\Common Files\Microsoft Lync Server 2010\DbSetup\xdssetup.wsf" /dbexists /sqlserver:lync2010lab.iwglab2.local\rtc /publisheracct:IWGLAB2\RTCUniversalServerAdmins /replicatoracct:IWGLAB2\RTCUniversalConfigReplicator /consumeracct:IWGLAB2\RTCUniversalReadOnlyAdmins /role:master /verbose
---------------
Installed SQL Server 2005 Backward Compatibility version is 8.05.2312
Connecting to SQL Server on lync2010lab.iwglab2.local\rtc
SqlMajorVersion : 10
SqlMinorVersion : 0
SqlBuildNo : 2531
SQL version is acceptable: 10.0.2531.0
Opened database xds
Db schema version is 0
Db sproc version is 0
Database exists, but needs to be installed with /clean.
---------------
Exit code: ERROR_DATABASE_REQUIRES_CLEAN (-25)
When running /dbexists, non-zero exit codes are not necessarily errors
---------------

Running script: C:\Windows\system32\cscript.exe //Nologo "C:\Program Files\Common Files\Microsoft Lync Server 2010\DbSetup\xdssetup.wsf" /sqlserver:lync2010lab.iwglab2.local\rtc /publisheracct:IWGLAB2\RTCUniversalServerAdmins /replicatoracct:IWGLAB2\RTCUniversalConfigReplicator /consumeracct:IWGLAB2\RTCUniversalReadOnlyAdmins /dbpath:C:\CsData\CentralMgmtStore\rtc\dbpath /logpath:C:\CsData\CentralMgmtStore\rtc\logpath /role:master /verbose
---------------
Installed SQL Server 2005 Backward Compatibility version is 8.05.2312
Connecting to SQL Server on lync2010lab.iwglab2.local\rtc
SqlMajorVersion : 10
SqlMinorVersion : 0
SqlBuildNo : 2531
SQL version is acceptable: 10.0.2531.0
Opened database xds
Db schema version is 0
Db sproc version is 0
(Major upgrade of database required.)

Due to schema changes this database cannot be re-used. It must be dropped and a new one created.
To preserve data, you must use this product's backup/export restore/import solution. Examine the product documentation for instructions.
---------------
Exit code: ERROR_NEED_MAJOR_UPGRADE_USE_IMP_EXP (-50)

How Could I publish my topology?

 

September 21st, 2010 6:44pm

How did you installed SQL ?
Free Windows Admin Tool Kit Click here and download it now
September 22nd, 2010 1:55am

Can you explain what steps you have done so far?

Schema/Forest/Domain Prep?

Is this an SE install? If so have you done the "Prepare first standard Edidtion server" step in the deployment wizard?

September 22nd, 2010 2:22am

It's a SE install

I did the the "Prepare first standard Edidtion server" step, I saw that step installed SQL.

I lanched the Schema/Forest/Domain prep steps directly on the DC and after on my Lync server I continued with "Prepare first standard Edidtion server" step

Regards

Free Windows Admin Tool Kit Click here and download it now
September 22nd, 2010 8:42am

Hello.. I am getting the same/similar error message. I have tried several times to publish the topology. All attempts have failed. I have even redeployed the member server with a new instantiation of the OS (W2K8R2) with all patches. Current environment is Hyper-V hosting a single DC (with AD integrated DNS and DHCP) and a member server for the new Lync RC. This is purely a lab environment and is a fresh build on the DC and member server.

I have been using the MS Lync Server 2010 Walkthrough document as my guide for this lab. I have also used four part series at http://blogs.technet.com/b/mbaher/ .

My log looks similar to what iwgroup posted and my log is posted below. I changed the domain name to protect corp identity.

Any help would be appreciated.

TIA

Running script: C:\Windows\system32\cscript.exe //Nologo "C:\Program Files\Common Files\Microsoft Lync Server 2010\DbSetup\xdssetup.wsf" /dbexists /sqlserver:fe.lync-lab.mylab.local\rtc /publisheracct:lync-lab\RTCUniversalServerAdmins /replicatoracct:lync-lab\RTCUniversalConfigReplicator /consumeracct:lync-lab\RTCUniversalReadOnlyAdmins /role:master /verbose
---------------
Installed SQL Server 2005 Backward Compatibility version is 8.05.2312
Connecting to SQL Server on fe.lync-lab.mylab.local\rtc
SqlMajorVersion : 10
SqlMinorVersion : 0
SqlBuildNo : 2531
SQL version is acceptable: 10.0.2531.0
Database does not exist.
---------------
Exit code: ERROR_NO_DATABASE_EXISTS (-23)
When running /dbexists, non-zero exit codes are not necessarily errors
---------------

Running script: C:\Windows\system32\cscript.exe //Nologo "C:\Program Files\Common Files\Microsoft Lync Server 2010\DbSetup\xdssetup.wsf" /sqlserver:fe.lync-lab.mylab.local\rtc /publisheracct:lync-lab\RTCUniversalServerAdmins /replicatoracct:lync-lab\RTCUniversalConfigReplicator /consumeracct:lync-lab\RTCUniversalReadOnlyAdmins /dbpath:C:\CsData\CentralMgmtStore\rtc\dbpath /logpath:C:\CsData\CentralMgmtStore\rtc\logpath /role:master /verbose
---------------
Installed SQL Server 2005 Backward Compatibility version is 8.05.2312
Connecting to SQL Server on fe.lync-lab.mylab.local\rtc
SqlMajorVersion : 10
SqlMinorVersion : 0
SqlBuildNo : 2531
SQL version is acceptable: 10.0.2531.0
(Database doesn't exist. Performing clean install.)
Creating database xds
    DbFile : PhysicalName = c:\csdata\centralmgmtstore\rtc\dbpath\xds.mdf
    LogFile: PhysicalName = c:\csdata\centralmgmtstore\rtc\logpath\xds.ldf
Executing batch dbcommon.sql on xds
Executing resource SetDbRoles on xds
Executing batch xds.sql on xds
Setting master role
Executing resource SetMaster on xds
Executing resource DbReIndex on xds
Setting security in xds
DbOwner is now sa
 lync-lab\RTCUniversalConfigReplicator is not a valid SQL login. A SQL login with this name will be created.
lync-lab\RTCUniversalConfigReplicator has a Win32_Account instance of SIDType 2
Global.SqlDmo.Logins.Add failed for lync-lab\RTCUniversalConfigReplicator

---------------
Exit code: ERROR_INVALID_ACCOUNT (-20)
---------------

September 22nd, 2010 11:50pm

Hi ,

Similar issue for me..

Regards

Vikas Sankla

Free Windows Admin Tool Kit Click here and download it now
September 25th, 2010 2:17pm

I encountered the same errors when trying to publish the topology on my window 2008 r2 vmware vm that had all the required prerequisite s/w installed and finally figured out from the administrative events that the SID of all my vms were the SAME which is a problem contrary to what i've seen posted by others.  So i unjoined all my VMs except for the DC from the domain, ran SYSPREP on them which configured new, unique SIDs, rejoined them to the domain after reconfiguring their fqdn and network settings.  I then had to uninstall all the Lync and SQL software from the server where i was trying to publish the topology and then went back through the deployment and topology publishing without any problems.  Trying to re-publish without the uninstall/re-install just triggered more problems.

----------------------------------------------------------------------------------------------------------------

....
Global.SqlDmo.Logins.Add failed for IWGLAB2\RTCUniversalConfigReplicator

---------------
Exit code: ERROR_INVALID_ACCOUNT (-20)
---------------


---------------
Installed SQL Server 2005 Backward Compatibility version is 8.05.2312
Connecting to SQL Server on lync2010lab.iwglab2.local\rtc
SqlMajorVersion : 10
SqlMinorVersion : 0
SqlBuildNo : 2531
SQL version is acceptable: 10.0.2531.0
Opened database xds
Db schema version is 0
Db sproc version is 0
Database exists, but needs to be installed with /clean.
---------------
Exit code: ERROR_DATABASE_REQUIRES_CLEAN (-25)
When running /dbexists, non-zero exit codes are not necessarily errors
---------------

...

..


---------------
Installed SQL Server 2005 Backward Compatibility version is 8.05.2312
Connecting to SQL Server on lync2010lab.iwglab2.local\rtc
SqlMajorVersion : 10
SqlMinorVersion : 0
SqlBuildNo : 2531
SQL version is acceptable: 10.0.2531.0
Opened database xds
Db schema version is 0
Db sproc version is 0
(Major upgrade of database required.)

Due to schema changes this database cannot be re-used. It must be dropped and a new one created.
To preserve data, you must use this product's backup/export restore/import solution. Examine the product documentation for instructions.
---------------
Exit code: ERROR_NEED_MAJOR_UPGRADE_USE_IMP_EXP (-50)

-------------------------------------------------------------------------------------------

John

September 26th, 2010 2:26pm

Solved!

Run sysprep before start your deployment!

Thanks to all

iwgroup

Free Windows Admin Tool Kit Click here and download it now
September 26th, 2010 11:06pm

Hi.. this is interesting.. because I ran sysprep when creating the initial OS image. First boot of each OS image said prepparing for first boot/run. I will check the SID's when I get to the office.

Kevin

  • Proposed as answer by Damon Anderson Wednesday, June 08, 2011 1:42 PM
September 27th, 2010 3:54pm

I looked at the SID in each of my instances of w2k8r2. I was surprised to find them all the same. I thought I had correctly run sysprep on my template image. Apparently not! I then deployed a brand new vhd and installed a fresh copy of w2k8r2 so that I was guaranteed to have a fresh SID. I confirmed that it was unique. At that time the installation of Lync Server 2010 RC went smoothly using that VHD. I will confirm my process of deploying VHD and new OS's does indeed produce new and unique SID. So at this point my Lync server is entering a test and learning phase.

 

Thanks,

Kevin

MCSA MCSE

  • Proposed as answer by Hasan Güral Thursday, October 28, 2010 8:41 PM
Free Windows Admin Tool Kit Click here and download it now
September 28th, 2010 7:11pm

Hi ,

Do you have that can solve?

Thanks,

October 28th, 2010 11:43pm

Hi All,

I was also getting

Exit Code: ERROR_NO_DATABASE_EXISTS (-23)

then

Failed to create database xds

Error (

name: Error

description:

number: -2147216371

message:

)

Exit code: ERROR_CREATE_DB (-4)

For me, it was because

  1. I'd created a D: partition for the share, then modified the NTFS permissions to remove everyone except
    SYSTEM
    Administrators
    [this is (arguably!) good security practice; default NTFS permissions allow anyone to create files/folders]
  2. As part of the installation, Lync had decided to put the database on D: (rather than C:) and somehow didn't have enough permissions.

As a workaround (for this lab environment!) I simply granted Everyone Full Control NTFS permissions - publishing then works!  I do still get completed with errors, but at least I'm making progress!

[not an SQL expert and Lync documentation somewhat lacking at the moment!]

Hope this helps someone!

Kind regards,

Anwar

Free Windows Admin Tool Kit Click here and download it now
November 10th, 2010 2:10pm

I've got a similar problem here.

At the end of the intsallation, I got

Setting security in xds
DbOwner is now sa
domain\RTCUniversalConfigReplicator is not a valid SQL login. A SQL login with this name will be created.
domain\RTCUniversalConfigReplicator has a Win32_Account instance of SIDType 2
Global.SqlDmo.Logins.Add failed for domain\RTCUniversalConfigReplicator

---------------
Exit code: ERROR_INVALID_ACCOUNT (-20)

As tried to login to the sql instance and add the RTCUniversalConfigReplicator from AD to the security users with sysadmin persmissions. I got a SQL error that the account was not found. Very strange as Active Directory did show me the account when I looked for it...

Offcourse the installation wizard gives me the same error because it cannot find this account

Any ideas? All teh other parts of the Lync Installation went fine in our sbs 2008 domain.

 

December 27th, 2010 9:17pm

Hi!

 

In my case it weren't the permissions, the installation decided to set up the Database-files on a compressed drive / directory. So I just removed the checkbox for "compression", ans see: The wizard finished without any errors :-)

 

Hope this helps!!

Greetz XandY

Free Windows Admin Tool Kit Click here and download it now
January 12th, 2011 2:54pm

Hello ,

 

I got this error which prevent me to proceed:

Running script: C:\Windows\system32\cscript.exe //Nologo "C:\Program Files\Common Files\Microsoft Lync Server 2010\DbSetup\xdssetup.wsf" /dbexists /sqlserver:lync.isc.com\rtc /publisheracct:ISC\RTCUniversalServerAdmins /replicatoracct:ISC\RTCUniversalConfigReplicator /consumeracct:ISC\RTCUniversalReadOnlyAdmins /role:master /verbose
---------------
Installed SQL Server 2005 Backward Compatibility version is 8.05.2312
Connecting to SQL Server on lync.isc.com\rtc
SqlMajorVersion : 10
SqlMinorVersion : 0
SqlBuildNo : 2531
SQL version is acceptable: 10.0.2531.0
Default database data file path is c:\Program Files\Microsoft SQL Server\MSSQL10.RTC\MSSQL\Data
Default database data file path is c:\Program Files\Microsoft SQL Server\MSSQL10.RTC\MSSQL\Data
Default database log file path is c:\Program Files\Microsoft SQL Server\MSSQL10.RTC\MSSQL\Data
Opened database xds
Db schema version is 0
Db sproc version is 0
Database exists, but needs to be installed with /clean.
---------------
Exit code: ERROR_DATABASE_REQUIRES_CLEAN (-25)
When running /dbexists, non-zero exit codes are not necessarily errors
---------------

Running script: C:\Windows\system32\cscript.exe //Nologo "C:\Program Files\Common Files\Microsoft Lync Server 2010\DbSetup\xdssetup.wsf" /sqlserver:lync.isc.com\rtc /publisheracct:ISC\RTCUniversalServerAdmins /replicatoracct:ISC\RTCUniversalConfigReplicator /consumeracct:ISC\RTCUniversalReadOnlyAdmins /dbpath:C:\CsData\CentralMgmtStore\rtc\dbpath /logpath:C:\CsData\CentralMgmtStore\rtc\logpath /role:master /verbose
---------------
Installed SQL Server 2005 Backward Compatibility version is 8.05.2312
Connecting to SQL Server on lync.isc.com\rtc
SqlMajorVersion : 10
SqlMinorVersion : 0
SqlBuildNo : 2531
SQL version is acceptable: 10.0.2531.0
Opened database xds
Db schema version is 0
Db sproc version is 0
(Major upgrade of database required.)

Due to schema changes this database cannot be re-used. It must be dropped and a new one created.
To preserve data, you must use this product's backup/export restore/import solution. Examine the product documentation for instructions.
---------------
Exit code: ERROR_NEED_MAJOR_UPGRADE_USE_IMP_EXP (-50)
---------------

Any suggestion ?

January 26th, 2011 11:31am

Amjed.Thuhly, look here:

....

Db schema version is 0
Db sproc version is 0
(Major upgrade of database required.)

Due to schema changes this database cannot be re-used. It must be dropped and a new one created.
To preserve data, you must use this product's backup/export restore/import solution. Examine the product documentation for instructions.
---------------
Exit code: ERROR_NEED_MAJOR_UPGRADE_USE_IMP_EXP (-50)

.....

So, u can use sqlcmd tool to drop database 'xds' and this error go away

But i think, if u have this error, u have also topicstarter`s error, whith is solved by reisntall Lync and DC and using sysprep utility

Free Windows Admin Tool Kit Click here and download it now
January 26th, 2011 2:59pm

I am also facing the same problem.

I have a windows server 2008 R2 Enterprise trial Hyper V vhd image.

My Steps:

1. Run sysprep as soon as i started the machine

2. Update OS

3. Activate OS

4. Join domain. My DC is on another vhd image.

5. Did the steps http://www.ocspedia.com/fe/Install_Microsoft_Lync_Server_2010.aspx?ArticleID=103

 

And I too got an error similar to the ones above:

Setting security in xds
DbOwner is now sa
domain\RTCUniversalConfigReplicator is not a valid SQL login. A SQL login with this name will be created.
domain\RTCUniversalConfigReplicator has a Win32_Account instance of SIDType 2
Global.SqlDmo.Logins.Add failed for domain\RTCUniversalConfigReplicator

So, the accepted solution is not working in my case.

April 20th, 2011 2:01pm

@Philippe Devaux_

Did you ever find a solution to this problem?

Free Windows Admin Tool Kit Click here and download it now
April 27th, 2011 8:16pm

Solved!

Run sysprep before start your deployment!

Thanks to all

iwgroup


Based on http://support.microsoft.com/kb/816099 i have determined there are no duplicate SID's. Still, i get the ERROR_INVALID_ACCOUNT

--Log:

 

Running script: C:\Windows\system32\cscript.exe //Nologo "C:\Program Files\Common Files\Microsoft Lync Server 2010\DbSetup\xdssetup.wsf" /sqlserver:trlync01.training.kender.local\rtc /publisheracct:TRAINING\RTCUniversalServerAdmins /replicatoracct:TRAINING\RTCUniversalConfigReplicator /consumeracct:TRAINING\RTCUniversalReadOnlyAdmins /dbpath:C:\CsData\CentralMgmtStore\rtc\dbpath /logpath:C:\CsData\CentralMgmtStore\rtc\logpath /role:master /verbose
---------------
Installed SQL Server 2005 Backward Compatibility version is 8.05.2312
Connecting to SQL Server on trlync01.training.kender.local\rtc
SqlMajorVersion : 10
SqlMinorVersion : 0
SqlBuildNo : 2531
SQL version is acceptable: 10.0.2531.0
(Database doesn't exist. Performing clean install.)
Creating database xds
    DbFile : PhysicalName = c:\csdata\centralmgmtstore\rtc\dbpath\xds.mdf
    LogFile: PhysicalName = c:\csdata\centralmgmtstore\rtc\logpath\xds.ldf
Executing batch dbcommon.sql on xds
Executing resource SetDbRoles on xds
Executing batch xds.sql on xds
Setting master role
Executing resource SetMaster on xds
Executing resource DbReIndex on xds
Setting security in xds
DbOwner is now sa
 TRAINING\RTCUniversalConfigReplicator is not a valid SQL login. A SQL login with this name will be created.
TRAINING\RTCUniversalConfigReplicator has a Win32_Account instance of SIDType 2
Global.SqlDmo.Logins.Add failed for TRAINING\RTCUniversalConfigReplicator

So either this quistion is -NOT- solved or there are more possible causes for the problem.

May 17th, 2011 5:17pm

Dear iwgroup

I had run sysprep before LYNC server deployment.

But the error of below still occurs.>"<

The Lync server is Stardard Edition and O.S of server is Windows 2008 Server R2

Has any solutions??

Thanks....^^

***************************************

DbOwner is now sa
 XXXX\RTCUniversalConfigReplicator is not a valid SQL login. A SQL login with this name will be created.
XXXX\RTCUniversalConfigReplicator has a Win32_Account instance of SIDType 2
Global.SqlDmo.Logins.Add failed for XXXX\RTCUniversalConfigReplicator

---------------
Exit code: ERROR_INVALID_ACCOUNT (-20)
***************************************

Free Windows Admin Tool Kit Click here and download it now
July 11th, 2011 6:19am

Solved!

Run sysprep before start your deployment!

Thanks to all

iwgroup


Based on http://support.microsoft.com/kb/816099 i have determined there are no duplicate SID's. Still, i get the ERROR_INVALID_ACCOUNT

--Log:

 

Running script: C:\Windows\system32\cscript.exe //Nologo "C:\Program Files\Common Files\Microsoft Lync Server 2010\DbSetup\xdssetup.wsf" /sqlserver:trlync01.training.kender.local\rtc /publisheracct:TRAINING\RTCUniversalServerAdmins /replicatoracct:TRAINING\RTCUniversalConfigReplicator /consumeracct:TRAINING\RTCUniversalReadOnlyAdmins /dbpath:C:\CsData\CentralMgmtStore\rtc\dbpath /logpath:C:\CsData\CentralMgmtStore\rtc\logpath /role:master /verbose
---------------
Installed SQL Server 2005 Backward Compatibility version is 8.05.2312
Connecting to SQL Server on trlync01.training.kender.local\rtc
SqlMajorVersion : 10
SqlMinorVersion : 0
SqlBuildNo : 2531
SQL version is acceptable: 10.0.2531.0
(Database doesn't exist. Performing clean install.)
Creating database xds


... (surplus lines removed)

Global.SqlDmo.Logins.Add failed for TRAINING\RTCUniversalConfigReplicator

So either this question is -NOT- solved or there are more possible causes for the problem.


Hi all,

I've tripped up on this one as well!

Background - I've 7 VM's (4 x W2K8R2 and 3 x W7) set up on a 16GB laptop, and am following a walkthough of installing Lync SE. I'd just copied the VM's and have subsequently found the servers (at least) have identical SIDs. That's my error, now how to get around it?

After research I realised the "Publish Topology" wizard does 2 things. 1) creates the SQL database XDS, then 2) adds to the database's administration group.

If, like me, you hit the ERROR_INVALID_ACCOUNT (-20) problem, then fiddle around trying to fix it and RERUN the publish wizard, you'll then hit a different error, one caused because the XDS database schema now already exists (created on your first attempt) and cannot be re-used.

An earlier poster suggested that the XPS database can be dropped. Knowing little about SQL I scratched around and found how to do this. Here's some outputs from the log showing the failure, the commands to drop the database and the log after rerunning the wizard. By the way, my domain is contoso.net:

(Part of log at C:\Users\Administrator\AppData\Local\Temp\1\DbExists-CentralMgmtStore-lab-

se.contoso.net_rtc-[YYYY_MM_DD][HH_MM_SS].log). There are separate logs for each action performed - worth checking!!

Opened database xds
Db schema version is 0
Db sproc version is 0
(Major upgrade of database required.)

Due to schema changes this database cannot be re-used. It must be dropped and a new one created.
To preserve data, you must use this product's backup/export restore/import solution. Examine the product documentation for instructions.
---------------
Exit code: ERROR_NEED_MAJOR_UPGRADE_USE_IMP_EXP (-50)
---------------

My bit...

C:\>sqlcmd -S.\RTC
1> DROP DATABASE XTS
2> GO
1> QUIT

C:\>

(Run the "Publish Topology" wizard again)...
(Part of NEW log at C:\Users\Administrator\AppData\Local\Temp\1\DbExists-CentralMgmtStore-lab-se.contoso.net_rtc-[YYYY_MM_DD][HH_MM_SS].log)
0
Connecting to SQL Server on lab-se.contoso.net\rtc
SqlMajorVersion : 10
SqlMinorVersion : 0
SqlBuildNo : 2531
SQL version is acceptable: 10.0.2531.0
Default database data file path is c:\Program Files\Microsoft SQL Server\MSSQL10.RTC\MSSQL\Data
Default database data file path is c:\Program Files\Microsoft SQL Server\MSSQL10.RTC\MSSQL\Data
Default database log file path is c:\Program Files\Microsoft SQL Server\MSSQL10.RTC\MSSQL\Data
Database does not exist.
---------------
Exit code: ERROR_NO_DATABASE_EXISTS (-23)
When running /dbexists, non-zero exit codes are not necessarily errors
---------------

At this point, the database has been recreated and the wizard proceeds (again) to its second action, tries to set some group memberships and fails as previously with ERROR_INVALID_ACCOUNT (-20).

This still leaves me to solve that second error, which I believe is due to duplicate SIDs, wwhatever Mark (RESPECT!) says! Since elsewhere I've found accounts of BIG problems with SQL after SYSGEN, now I'm going to revert to a VM snapshot and try SYSGEN to see if that problem goes away.

I have to say I think it's daft of MS to make the wizard do 2 separate things, either of which can fail and then leave the user to manually drop the database after he may have corrected the account problem. The script should be spilt into 2 parts!

I'll report back with my SYSGEN findings.

Richard

 

August 4th, 2011 8:26pm

Running script: C:\Windows\system32\cscript.exe //Nologo "C:\Program Files\Common Files\Microsoft Lync Server 2010\DbSetup\xdssetup.wsf" /sqlserver:lync2010.microsoft.com.pk\rtc /publisheracct:MICROSOFT\RTCUniversalServerAdmins /replicatoracct:MICROSOFT\RTCUniversalConfigReplicator /consumeracct:MICROSOFT\RTCUniversalReadOnlyAdmins /dbpath:C:\CsData\CentralMgmtStore\rtc\dbpath /logpath:C:\CsData\CentralMgmtStore\rtc\logpath /role:master /verbose --------------- Installed SQL Server 2005 Backward Compatibility version is 8.05.2312 Connecting to SQL Server on lync2010.microsoft.com.pk\rtc SqlMajorVersion : 10 SqlMinorVersion : 0 SqlBuildNo : 2531 SQL version is acceptable: 10.0.2531.0 Opened database xds Db schema version is 0 Db sproc version is 0 (Major upgrade of database required.) Due to schema changes this database cannot be re-used. It must be dropped and a new one created. To preserve data, you must use this product's backup/export restore/import solution. Examine the product documentation for instructions. --------------- Exit code: ERROR_NEED_MAJOR_UPGRADE_USE_IMP_EXP (-50) --------------- C:\Users\Administrator>sqlcmd -S.\RTC 1> drop database XTS 2> go Msg 3701, Level 11, State 1, Server LYNC2010\RTC, Line 1 Cannot drop the database 'XTS', because it does not exist or you do not have per mission.
Free Windows Admin Tool Kit Click here and download it now
September 19th, 2011 1:44pm

Thanks to all for  kind help. My problem resolved. I was using both machine as VM's on same machine. What I did I used Domain Controller as VM and Lync Server also as VM. I put the Domain Controller VM on a different machine and install 2008R2 on a machine and then installed Lync Server then I did all initial configuration on Lync Server and started publishing Topology and this got successful.

 

What I feel that the main problem is the Domain Controller and the Lync Server cant be on the same machine.

September 22nd, 2011 2:54pm

Similar problem. Error to create the SQL DBs on a Standard Edition server (CMS isn't located on this server).

For me the problem was because the default Everyone ACE permission on root dir from drive C was missing. Grating Everyone permission to CsData folder was enough to solve the problem. After running the Setup or Remove Lync Server Components again, the DBs were created as expected and setup completed with success.

Free Windows Admin Tool Kit Click here and download it now
March 1st, 2012 5:15pm

Seems that no one shares the solution.

I'm having the same problem as well.

Error -20 Invalid User Account at the first go and then NEED_MAJOR_UPGRADE at the second run

This is the TS I've done so far:

- Dropping the SQL database (willmake it advance up to the stage when (-20) is threw.

- Working with domain Admin and included in all required groups

Currently Syspreping the server and giving it a try.

May 1st, 2012 11:47am

Still kicked out after syspreping the Server
  • Proposed as answer by Mohammed Ashaq Wednesday, June 27, 2012 9:37 AM
  • Unproposed as answer by Mohammed Ashaq Wednesday, June 27, 2012 9:37 AM
Free Windows Admin Tool Kit Click here and download it now
May 1st, 2012 12:06pm

Hi Everyone,

I had same error "Exit code: ERROR_CREATE_DB (-4)" . 

Step 1 : What i did removed Folder compression from D Drive on which i placed CsData folder and RtcReplicaRoot.

Step 2 : I Give full permission for above 2 folders i.e.  CsData folder and RtcReplicaRoot.

After executing above steps installatoin was run smoothly and finish successfully. :)

I was struggled for 2 week to fix this issue.

Thanks and warm regards,

June 27th, 2012 12:41pm

Holy crap! Folder compression was the problem for me too. Only one week spent on it.
Free Windows Admin Tool Kit Click here and download it now
November 6th, 2012 12:37am

*Install SQL Management Studio

*Connect to the database engine instance

*Delete xds db

*Rerun Publish topology

May 6th, 2013 1:36pm

Ultimately below command worksafter three days of efforts. thanks a lot 

but need to drop both the database XDS and LIS. single will not work. also sysprep does not do anything for this issue. only waste your hours. 

C:\>sqlcmd -S.\RTC
1> DROP DATABASE XTS
2> GO
1> QUIT

Free Windows Admin Tool Kit Click here and download it now
June 21st, 2013 11:49am

this did the trick... thanks
September 16th, 2013 11:58am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics