Showing posts with label SQL. Show all posts
Showing posts with label SQL. Show all posts

Tuesday, August 21, 2012

Lync Topology publishing error

Error: Script failed (code "ERROR_VALIDATE_BAD_SQL_VERSION") when installing "CentralMgmtStore" on "<systenmane>.lynctest.com". For details, see the following log file: "C:\Users\Administrator.LYNCTEST\AppData\Local\Temp\2\Create-CentralMgmtStore-<systemname>.lynctest.com-[2012_08_21][14_31_26].log"

Error: An error occurred: "Microsoft.Rtc.Common.Data.SqlConnectionException" "Cannot open database "xds" requested by the login. The login failed.
Login failed for user 'LYNCTEST\Administrator'."

Running script: C:\Windows\system32\cscript.exe //Nologo "C:\Program Files\Common Files\Microsoft Lync Server 2010\DbSetup\xdssetup.wsf" /dbexists /sqlserver:<systemname>.lynctest.com /publisheracct:LYNCTEST\RTCUniversalServerAdmins /replicatoracct:LYNCTEST\RTCUniversalConfigReplicator /consumeracct:LYNCTEST\RTCUniversalReadOnlyAdmins /role:master /verbose
---------------
Installed SQL Server 2005 Backward Compatibility version is 8.05.2312
Connecting to SQL Server on <systemname>.lynctest.com
SqlMajorVersion : 10
SqlMinorVersion : 0
SqlBuildNo : 1600
Error: SQL version is not high enough. SQL Server 2005 must be major version 9 and build 4035(SP3) or higher. SQL Server 2008 must be major version 10 and build 2531(SP1) or higher. SQL Server 2008 R2 must be minor version 50 and build 1600 or higher. This SQL Server is major version 10, minor version 0 and build 1600.
---------------
Exit code: ERROR_VALIDATE_BAD_SQL_VERSION (-28)
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:<systemname>.lynctest.com /publisheracct:LYNCTEST\RTCUniversalServerAdmins /replicatoracct:LYNCTEST\RTCUniversalConfigReplicator /consumeracct:LYNCTEST\RTCUniversalReadOnlyAdmins /dbpath:"C:\CsData\CentralMgmtStore\(default)\dbpath" /logpath:"C:\CsData\CentralMgmtStore\(default)\logpath" /role:master /verbose
---------------
Installed SQL Server 2005 Backward Compatibility version is 8.05.2312
Connecting to SQL Server on <systemname>.lynctest.com
SqlMajorVersion : 10
SqlMinorVersion : 0
SqlBuildNo : 1600
Error: SQL version is not high enough. SQL Server 2005 must be major version 9 and build 4035(SP3) or higher. SQL Server 2008 must be major version 10 and build 2531(SP1) or higher. SQL Server 2008 R2 must be minor version 50 and build 1600 or higher. This SQL Server is major version 10, minor version 0 and build 1600.
---------------
Exit code: ERROR_VALIDATE_BAD_SQL_VERSION (-28)

------------------
Other relative errors

Error: An error occurred: "Microsoft.Rtc.Common.Data.SqlConnectionException" "Cannot open database "xds" requested by the login. The login failed.
Login failed for user 'LYNCTEST\Administrator'."

Error: Script failed (code "ERROR_VALIDATE_BAD_SQL_VERSION") when installing "CentralMgmtStore" on "<Systemname>.lynctest.com". For details, see the following log file: "C:\Users\Administrator.LYNCTEST\AppData\Local\Temp\2\Create-CentralMgmtStore-<Systemname>.lynctest.com-[2012_08_21][14_44_59].log"
  and in this doc it is showing the DB is not
compatible with the version
"Error: SQL version is not high enough. SQL Server 2005 must be major version 9 and build 4035(SP3) or higher. SQL Server 2008 must be major version 10 and build 2531(SP1) or higher. SQL Server 2008 R2 must be minor version 50 and build 1600 or higher. This SQL Server is major version 10, minor version 0 and build 1600."

Error: An error occurred: "Microsoft.Rtc.Common.Data.SqlConnectionException" "Cannot open database "xds" requested by the login. The login failed.
Login failed for user 'LYNCTEST\Administrator'."

-----------------------
One solution  as below

Solution :

The first part of  errors mainly due to the SQL server connectivity and  second part is with the compatibility issue
. Check the SQL server whether named pipe and TCP/IP configuration have enabled or not. Also check whether  the required ports are enabled on the SQL server firewall, you will be able to solve the first part.

Install the service pack of SQL  2008 to rectify the second issue


Monday, February 13, 2012

PLEASE IGNORE - Temporary item created by Microsoft Conferencing Add-in for Outlook (Version 8.0.6362.187)



Error

I faced similar issue with Conferencing add-in Version 8.0.6362.143 and 8.0.6362 .187 versions .And users were receiving empty appointments in their calendar. With subject line

PLEASE IGNORE - Temporary item created by Microsoft Conferencing Add-in for Outlook (Version 8.0.6362.187)


Resolution
I updated the Conferencing add-in with Version 8.0.6362.190 (or above will help ) and resolved the issue

Thursday, February 9, 2012

Rule "Reporting Services Catalog Temporary Database File Existence" failed.

Error :

Rule "Reporting Services Catalog Temporary Database File Existence" failed.

Solution

Open the folder
"C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA"
Delete the below files from the folder

ReportServer.mdf
ReportServer_log.LDF
ReportServerTempDB.mdf
ReportServerTempDB_log.LDF

After deleting the above files ,click Re-run in the setup window

Rule "Reporting Services Catalog Database File Existence" failed


Error :
Rule "Reporting Services Catalog Database File Existence" failed

Solution

Open the folder
"C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA"
Delete the below files from the folder

ReportServer.mdf
ReportServer_log.LDF
ReportServerTempDB.mdf
ReportServerTempDB_log.LDF

After deleting the above files ,click Re-run in the setup window


Friday, February 3, 2012

Invoke or BeginInvoke cannot be called on a control until the window handle has been created (Solved)


Issue
I was trying to install SLL 2008 in a windows 2008 R2 64 Bit server and I faced an error while installation.

Error
SQL Server Setup has encountered the following error:

Invoke or BeginInvoke cannot be called on a control until the window handle has been created

Resolution (1)
After clicking the setup.exe I have closed all the explorer windows and tried to install and the issue didn’t happened again and I was able to install SQL

Resolution (2)
Restart the server first
Open the folder in which you have the SQL installer files.
Open the folder which suits your OS (X86 or X64) and find the file "LandingPage.exe"
Double click on it.
It will ask for the installer folder, select the parent installer folder and click OK.
Then the normal SQL installation pop up will come .
Close all windows other than this setup window (recommended), and do the installation