SQL Server 2005 Installation Error
I am installine ECC6 on SQL Serer 2006. I have started the SQL Server installation, using the SQL4SAP.vbs and after about 10 minutes the installation stops with an error. I am pointed to a fine Summary.txt but the details in the file do not give a clue on the problem:
Machine : SAPDEMO
Product : SQLXML4
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_SQLXML4_1.log
SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt.
Time : Mon Dec 03 09:09:38 2007
List of log files:
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_Core(Local).log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_SQLSupport_1.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_SQLNCLI_1.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_OWC11_1.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_SqlWriter_1.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_BackwardsCompat_1.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_MSXML6_1.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_SQLSupport_2.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_SQLNCLI_2.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_OWC11_2.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_BOL_1.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_BackwardsCompat_2.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_SQLXML4_1.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_Datastore.xml
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_.NET Framework 2.0.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_Core.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_.NET Framework 2.0 LangPack.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_.NET Framework Upgrade Advisor.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_.NET Framework Upgrade Advisor LangPack.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_.NET Framework Windows Installer.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_.NET Framework Windows Installer LangPack.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_SNAC.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_Support.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_SCC.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_WI.log
Hi Rajeev,
Indeed it was a typo error I am attempting SQL Server 2005.
I am using the 32 bit installation, that has been checked.
Here are the details from C:\Windows\SQL4SAP.log
Customized installation of SQL Server 2005 for SAP *
Log File: C:\WINDOWS\SQL4SAP.log
Script started 03/12/2007 08:46:25 on SAPDEMO
System settings:
Win32_Processor.Name=Intel(R) Core(TM)2 Duo CPU T7500 @ 2.20GHz
Win32_Processor.Name=Intel(R) Core(TM)2 Duo CPU T7500 @ 2.20GHz
Win32_ComputerSystem.SystemType=X86-based PC
Win32_OperatingSystem.OSType=18
Win32_OperatingSystem.Version=5.2.3790
Win32_OperatingSystem.ServicePackMajorVersion=2
Win32_OperatingSystem.Caption=Microsoft(R) Windows(R) Server 2003, Standard Edition
Win32_OperatingSystem.ProductType=3
Win32_OperatingSystem.OSProductSuite=272
Win32_OperatingSystem.OSLanguage=1033
Windows version:
OSVersion = 5.2
OSFamily = Windows2003
OSServicePack = 2
OSEdition = Server
OSSystemType = X86
OSProductSuite = Terminal Server
OSMsiVersion = 3.1.4000.4042
OSMdacVersion = 2.82.3959.0
OSLanguage = English United States
OSLanguageID = 1033
Environment on SAPDEMO:
userDir = C:\Documents and Settings\Administrator\
tmpDir = C:\DOCUME1\ADMINI1\LOCALS~1\Temp\1\
rootDir = C:\WINDOWS\
prgDir = C:\Program Files\
prgDirX86 = \
SQL4SAP version:
version: ' v3.2.44 Mar 2007: SQL2005 SP2, Windows2003 SP2
size: 86124
created: 30/11/2007 16:59:31
modified: 20/03/2007 13:36:44
exe: C:\WINDOWS\system32\cscript.exe
script: C:\SAP_CD\CD2\SQL4SAP.vbs
C: C:
Script path:
myRoot = C:\SAP_CD\CD2\
myDir = C:\SAP_CD\CD2\x86\
myDirUNC = C:\SAP_CD\CD2\x86\
Script settings:
SqlAuthInstall = False
SilentInstall = False
DeEditionOnly = False
DeEditionPossible = False
SapItMsgBox = False
SilentRtmSetup = True
Service Account:
"C:\SAP_CD\CD2\x86\SqlCmd\GetSidName.exe" S-1-5-18 =>NT AUTHORITY\SYSTEM
OSSystemAccount= NT AUTHORITY\SYSTEM
03/12/2007 08:46:28
Input Box "Select SQL Server instance"
No SQL Server instance was found.
SQL Server Native Client not installed
SQL Server 2005 Client Tools not installed
Enter a new or existing instance name.
- for a Default Instance, enter: (default) or .
- for a Named Instance, enter: <SID>
To install SQL Client Tools Only, press Cancel.
Result: (default)
Registry settings (1/2):
HKLM\SOFTWARE\Microsoft\DataAccess\FullInstallVer
READ: 2.82.3959.0
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\{3d06c673-5e8a-41c0-b47f-3c3ca0a22e67}
READ: 4
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\{3d06c673-5e8a-41c0-b47f-3c3ca0a22e67}
WRITE(REG_DWORD): 4
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\{319b29ae-7427-4fbc-9355-22df056c27a4}
READ: 4
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\{319b29ae-7427-4fbc-9355-22df056c27a4}
WRITE(REG_DWORD): 4
HKLM\SOFTWARE\Microsoft\Microsoft SQL Native Client\CurrentVersion\Version
READ:
HKLM\SOFTWARE\Microsoft\Microsoft SQL Native Client\CurrentVersion\PatchLevel
READ:
HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\90\Tools\ClientSetup\CurrentVersion\CurrentVersion
READ:
HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\90\Tools\ClientSetup\CurrentVersion\CSDVersion
READ:
03/12/2007 08:46:32
Message Box "Confirmation"
You have chosen to install the new instance
SQL Instance: (default)
SQL Version: 9.00.3042
SQL Edition: 2005 Enterprise Edition
SQL Collation: SQL_Latin1_General_CP850_BIN2
Authentication: Windows only
Login sa: random password, login disabled
=======================================
The installation may take 15 minutes or longer
=======================================
Do you want to start the installation now?
Result: vbOK
03/12/2007 08:46:34
installing SQL Server 2005 Enterprise Edition on X86 - build 9.00.1399 ...
Log File: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt
Command: "C:\SAP_CD\CD2\x86\EnterpriseEdition\Servers\setup.exe" /qn USERNAME="SAP ISV Royalty Licensing Program" ADDLOCAL=Connectivity,SQL_Tools90,SQLXML,Tools_Legacy,SQL_Documentation,SQL_BooksOnline,SQL_Data_Files,SQL_FullText PERSEAT=50 INSTANCENAME=MSSQLSERVER SQLCOLLATION=SQL_Latin1_General_CP850_BIN2 AGTAUTOSTART=1 SQLACCOUNT="NT AUTHORITY\SYSTEM" AGTACCOUNT="NT AUTHORITY\SYSTEM" SQLBROWSERACCOUNT="NT AUTHORITY\SYSTEM" DISABLENETWORKPROTOCOLS=0 SAPWD=xxxxxxxxxxxxxxxx
Return Code: 1605
03/12/2007 08:48:41
Log file C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt
Microsoft SQL Server 2005 9.00.1399.06
==============================
OS Version : Microsoft Windows Server 2003 family, Standard Edition Service Pack 2 (Build 3790)
Time : Mon Dec 03 08:46:48 2007
Machine : SAPDEMO
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SQLSupport_1.log
Machine : SAPDEMO
Product : Microsoft SQL Server Native Client
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SQLNCLI_1.log
Machine : SAPDEMO
Product : Microsoft SQL Server VSS Writer
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SqlWriter_1.log
Machine : SAPDEMO
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SQLSupport_2.log
Machine : SAPDEMO
Product : Microsoft SQL Server Native Client
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SQLNCLI_2.log
Machine : SAPDEMO
Product : Microsoft SQL Server 2005 Books Online (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_BOL_1.log
Machine : SAPDEMO
Product : SQLXML4
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SQLXML4_1.log
SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt.
Time : Mon Dec 03 08:48:39 2007
List of log files:
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_Core(Local).log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SQLSupport_1.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SQLNCLI_1.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SqlWriter_1.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_MSXML6_1.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SQLSupport_2.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SQLNCLI_2.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_BOL_1.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SQLXML4_1.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_Datastore.xml
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_.NET Framework 2.0.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_Core.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_.NET Framework 2.0 LangPack.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_.NET Framework Upgrade Advisor.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_.NET Framework Upgrade Advisor LangPack.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_.NET Framework Windows Installer.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_.NET Framework Windows Installer LangPack.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SNAC.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_Support.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SCC.log
service MSSQLSERVER does not exist
03/12/2007 08:48:41
Message Box "Installation failed"
The unattended installation failed.
Installation Step: SQL Server - build 9.00.1399
Return Code: 1605
Log File: C:\WINDOWS\SQL4SAP.log
Check the log file above!
See also SAP note 896566 for known issues
Result: vbOK
Registry settings (2/2):
HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names\SQL\MSSQLSERVER
READ:
HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg0
READ:
HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg1
READ:
HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg2
READ:
HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg3
READ:
HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg4
READ:
HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg5
READ:
HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg6
READ:
HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg7
READ:
HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg8
READ:
HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg9
READ:
HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg10
READ:
HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg11
READ:
HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg12
READ:
HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg13
READ:
HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg14
READ:
HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg15
READ:
HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg16
READ:
HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg17
READ:
HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg18
READ:
HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg19
READ:
HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg20
READ:
HKLM\SOFTWARE\Microsoft\MSSQLSERVER\Setup\SQLPath
READ:
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\{3d06c673-5e8a-41c0-b47f-3c3ca0a22e67}
WRITE(REG_DWORD): 4
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\{319b29ae-7427-4fbc-9355-22df056c27a4}
WRITE(REG_DWORD): 4
03/12/2007 08:48:47
Quit script with return code 1
Similar Messages
-
How retrieving the product key for a SQL Server 2005 installation
Hi,
is it possible to retrieve the product key associated to a SQL Server 2005 installation?
If yes, how?
Many thanksHello,
The following tool may provide you the product key for SQL Server 2005 and SQL Server 2008 instances.
http://www.nirsoft.net/utils/product_cd_key_viewer.html
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com -
SQL Server 2005 installation after VS 2005 installation
I saw in another thread that someone had trouble installing SQL Server 2005 after installing Visual Studio 2005. The answer alluded to the fact that the default/standard installation of VS 2005 results in the installation of SQL Server Express at the same time.
I installed Visual Studio 2005 Professional on my PC already, and am about to install SQL Server 2005 Developer edition. Is there any way to know now (before installing SQL Server) that something will cause an installation issue? I would like to do whatever I can to prevent problems in advance, so is there anything I can / should to before installing SQL Server?I did not mention in my previous post that after much reading in help forums and treading on proverbial eggshells (hoping I was doing things correctly to ensure good installation of purchased products thereafter), I recently uninstalled/removed several beta versions of Visual Studio and SQL Server from my personal/home PC (O/S: Windows XP Media Center Edition Version 5.1, build 2600, SP2). I have already jumped over the "uninstall wall" several times to get to this point. That is why I am proceeding with caution, to avoid any more torture; I would prefer to do the right thing (even though I've apparently already started down the wrong path) to avoid any more headaches.
I was unsure at first, but went in search of logs and registry entries to see if SQL Express was installed, and am now fairly sure it was, because of 4 items I found:
1) In C:\Program Files\Microsoft Visual Studio 8\Microsoft Visual Studio 2005 Professional Edition - ENU\Logs\dd_vsinstall80.txt:
[04/29/08,13:10:53] Microsoft SQL Server 2005 Express Edition x86: e:\setup\..\wcu\sse\SQLEXPR32.EXE exited with return value 0
[04/29/08,13:10:53] InstallReturnValue: GFN_MID SSE x86, 0x0
[04/29/08,13:10:53] Microsoft SQL Server 2005 Express Edition x86: Error code 0 for this component means "The operation completed successfully."
2) In: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\
SQLSetup0006_D8GKLNB1_SQL.log:
MSI (s) (34:88) [13:10:15:218]: Product: Microsoft SQL Server 2005 Express Edition -- Installation completed successfully.
3) Add/Remove Programs shows “Microsoft SQL Server 2005” is on my machine (although “Express” is not part of the name). Also listed are: Microsoft SQL Server Native Client, Microsoft SQL Server Setup Support Files (English), Microsoft SQL Server VSS Writer, MSXML 6.0 parser
4) Searching for InstallDate in regedit: HKLM|Software\Microsoft\Windows\CurrentVersion\Intaller\UserData\5-1-5-18\Products\7DDFFFA258DE09A4C
DisplayName Microsoft SQL Server 2005 Express Edition
InstallDate same date as Visual Studio 2005 installation
InstallSource l:\f58e49f47a1d350886021c2b2dd1\Setup\
So now I would like to know what the best course of action is to remedy this with the least amount of aggravation. Is it possible to just use A/R programs to uninstall the components of SQL Server 2005 (Express) that interfere with installation of SQL Server 2005 Developer edition? Would those be the workstation components? -
MX7 SQL Server 2005 datasoucre error
Webserver is Windows 2003 RC2, MX7.02
SQL Server is Windows 2003 RC2, SQL Server 2005 (9.0.1399)
CF and SQL are on seperate machines
[edit: the fix]
OK, gotta love those netops guys.
So we were narrowing it down to server -> server
communication issues...specifically windows authentication.
We set up a SQL Server user on the SQL Server and set up the
datasource in coldfusion that used that SQL Server user (not
DOMAIN\user, just user) and skipped the whole System DSN on the
webserver and it works.
So the long and the short of it is that there seems to be
some network trust issue between our app server (cf) and our db
server (sql) and we are unable to set up datasources the way we
used to (from win2k/cf5 -> win2k3/sql2005). Oh well.
[/edit]
[Edit: additional info]
SQL Server logs give this error message:
Error: 18456, Severity: 14, State: 6.
I've looked up this error message on msdn (
http://blogs.msdn.com/sql_protocols/archive/2006/02/21/536201.aspx)
and they say it means "Attempt to use a Windows login name with SQL
Authentication"
I've made sure that SQL Server is running in "SQL Server and
Windows Authentication Mode" (and restarted). No change. Of course
Adobe says that you HAVE to use "SQL Server and Windows
Authentication Mode" and Microsoft say the fix to the error is to
chose "Windows Authentication Mode". Grrr.
I've tried changing the JDBC URL to the IP of the SQL Server
and I get the same error mesaage. I purposely fudge the IP and I
get a totally different "time out" error (duh ;^) So something
about the way Cold Fusion talks to SQL Server isn't quite right.
I feel dumb asking this, but is there any specific
documentation about connecting MX7 to SQL Server 2005? The
documenation on livedocs refers to SQL Server 2000 (I think...but
I'm sure it's not talking about 2005). I'm beginning to wonder if
there is some stupid little step that I missed somewhere along the
way when setting things up...*sigh*
[/Edit]
I get the following error when attempting to set up the
datasource in Coldfusion administrator:
Connection verification failed for data source: wamaxDS
com.microsoft.sqlserver.jdbc.SQLServerException: Login failed
for user 'UWT\cfusion2'.
The root cause was that:
com.microsoft.sqlserver.jdbc.SQLServerException: Login failed for
user 'UWT\cfusion2'.
Now, I've got our production box which is running CF 5
connecting to the same database on the same SQL server and does NOT
get the 'Login failed for user' error...which leads me to believe
that it's not a simple permissions issue. To be clear my CF5 box
connects fine to the database. My CF7 box simply will not.
I've installed the latest JDBC drivers and set up a
datasource that generates the error above (I get the same error
when trying to set it up as "Microsoft SQL Server" with the obvious
exception of the driver in the error being different).
I've searched the forums and did the TCP/IP fix.
I've tried setting the ODBC DSN up in windows using "windows
authentication" and the "mixed mode"...I'm just lost here.
I've lost track of the combinations of things I've tried to
get this to work (ya know how you get into "try anything and pray
mode"?...that was me all day today).
Hopefully I've provided enough information to get someone
started on helping me. If I've left anything out, please chastise
me and then let me know what I need to let you know. Sorry if this
message is incoherent...my brain is mush *sigh*.Hi,
I presume, this is how you have placed your code
Code Snippet
-- Retrive the product archive record
select * from dbo.api_userArchive where isActive = 1
Seems just fine. Could you post the error. Also try posting the entire code
HTH,
Suprotim Agarwal
http://www.dotnetcurry.com -
SQL Server 2008 Installation Error
I found this error when i am try to Install SQL Server 2008 on Windows 8
TITLE: Microsoft SQL Server 2008 Setup
The following error has occurred:
Error getting file attributes for 1392. Please make sure that the drive is formatted and accessible.
For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.0.1600.22&EvtType=0xF45F6601%25401201%25401
BUTTONS:
OKHi,
Did you check what the message ask you to?
Are you using local disk for the installation? Are you trying to install on a disk different from the OS disk (C:\) ?
Please try to give more information.
[Personal Site] [Blog] [Facebook] -
Sql server 2012 installation error
can someone please tell me why i am getting an error when i am trying to install sql 2012 SP1. it when i get to the installation it says "sql server Setup has encountered the following error. hexadecimal value 0x00, is an invalid character.Line
1, position 51471. error code 0x84B10001.Hi vijatkumar.ptl,
According to your description and your error message, when you install SQL Server 2012, check if splinters of an MSDE instance (Microsoft Desktop Engine) was left over from other program. If this hidden instance exists, and the installer perform the RunDiscoveryAction
process, the issue will occur. So I recommend you manually remove a Microsoft SQL Server
Desktop Engine instance (MSDE) by using Add/Remove Programs in Control Panel, and so on, then reinstall again.
There is a similar issue about SQL Server 2012 setup issue, you can refer to the following posts.
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/72fbd726-730b-4aef-9db1-aeb8bfb5d334/sql-2012-setup-issues-hexadecimal-value-0x00-is-an-invalid-character
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/f37e18eb-f1ab-4106-83f6-8bbf04d6a41a/setup-failed-0x84b10001-sql-2012-hexadecimal-value-0x00-is-an-invalid-character-line-1-position?forum=sqlsetupandupgrade
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support -
SQL SERVER 2014 Installation error
Hi, I'm having great difficulty in installing SQL server 2014 developer edition 64- bit . When I use to run setup it says sql server boot strapper.dll is missing although it is present inside the folder and when I opened the sql setup bootstrapper.dll it
gives the error "This file doesn't have a program associated with it for performing this action". ? I've attached the snapshot of the error as well.
Needs immediate help.Hello,
Are you trying to install from a network share/location? Could you try to copy the media to a folder on the c:\ drive.
If the media is an .ISO file, please unzip it using WinRAR and install from that folder on the C:\ drive.
If the above does not help, could you try to download the media again.
The following article may be useful.
http://www.sqlcoffee.com/SQLServer2014_0005.htm
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com -
Error during installation of Microsoft SQL Server 2005
Hello All,
During installation of Microsoft SQL Server 2005 I have got the below error message
"There was an unexpected failure during the setup wizard"
From this link http://support.microsoft.com/kb/916760 i came to know that this error occurs just because I used SQL Server 2005 installations from a folder on a network share.
After that i unstall everything & copy the installations in a local drive. But again when we restart the activity we got the same error message & the installation completed.
Any hint why this happens..
Thank You.
Kind Regards,
JitudaHello Jituda,
I think we need to focus on the error in the setup log first.
Error: Action "InvokeSqlSetupDllAction" threw an exception during execution. Error information reported during run:
Source File Name: datastore\cachedpropertycollection.cpp
you might be able to see more detailed error information in the log.
You may check if the following links help:
http://www.sqlserverfaq.net/2008/12/17/sql-server-2005-setup-failing-to-install-on-cluster-with-unexpected-failure-while-performing-the-scc-checks/
http://social.msdn.microsoft.com/Forums/en-US/sqlsetupandupgrade/thread/f998b073-4378-4d02-95ac-c9afb31c7a60
In addition, to clarify, the SQL4SAP.VBS script does not support Microsoft Cluster Service (MSCS). If you want to run the
script in an MSCS configuration, you get an error message. In MSCS configuration need to install the SQL Server database software manually instead of using the script. Please see the corresponding SAP product installation guide under http://service.sap.com/instguides
Kind regards,
Qingqing Wang -
Error: [Microsoft][ODBC SQL Server Driver]Protocol error in TDS stream
hello,
our application vendors are receving the below errors while running their data load job.I spoke to our networking team member and he said everything looks good on the networking side .Can someone please help me with the below errors.we are using
Microsoft SQL Server 2012 (SP1) - 11.0.3000.0 (X64) Enterprise
Edition: Core-based Licensing (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1).
Windows OS:windows server 2008 R2 sp1
7280
6920
DBS-070401
6/5/2014 1:17:24 PM
|Data flow DIM_CONTRACT_SWAM_INIT_LOAD_DF|Loader Key_Generation_DIM_CONTRACT
7280
6920
DBS-070401
6/5/2014 1:17:24 PM
ODBC data source <HPWDBOE001> error message for operation <SQLExecute>: <[Microsoft][ODBC SQL Server
7280
6920
DBS-070401
6/5/2014 1:17:24 PM
Driver][DBNETLIB]ConnectionWrite (send()).
7280
6920
DBS-070401
6/5/2014 1:17:24 PM
[Microsoft][ODBC SQL Server Driver][DBNETLIB]General network error. Check your network documentation.>.
6760
6164
DBS-070401
6/5/2014 1:17:24 PM
|Data flow DIM_EMPLOYER_GROUP_SWAM_INIT_LOAD_DF|Reader TCRdr_9
6760
6164
DBS-070401
6/5/2014 1:17:24 PM
ODBC data source <serverName> error message for operation <SQLExecute>: <[Microsoft][ODBC SQL Server Driver]Protocol error in
6760
6164
DBS-070401
6/5/2014 1:17:24 PM
TDS stream
6760
6164
DBS-070401
6/5/2014 1:17:24 PM
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (recv()).
6760
6164
DBS-070401
6/5/2014 1:17:24 PM
[Microsoft][ODBC SQL Server Driver][DBNETLIB]General network error. Check your network documentation.>.
I googled and found the below link the below link which asked me to enable named pipes.I enabled
namped pipes in the sql server Network configuration.I havent yet restarted the sql services as this is a prod box.I will do it later in the evening today.
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/69149a71-3c15-4c95-9f95-a30db458abeb/sql-server-2005-communcations-errors-through-odbc?forum=sqldataaccess
Can someone help me with these errors.
Thanks
luckyThank you Erland.
I dont see any crash dumps in sql server.I checked the tcp chimney and its set to automatic.I am not knowing what to look at to resolve this issue.
if its the issue with the client API can i ask our vendor to check the client?
Our networking member gave the following report:
No problems on vlan 14 or your port the top is from the switch to your server then bottom is from my pc to your server
SP_DC_CORE_VSS# ping 10.10.12.228
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.10.12.228, timeout is 2 seconds:
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms
SP_DC_CORE_VSS#
lucky -
Different versions of SQL Server 2005 Developer Edition
Some of our business processes still use SQL Server 2005 and I need to install Developer Edition on my desktop.
I have following downloads available in my MSDN subscription (other than Itanium):
SQL Server 2005 Developer Edition - DVD (English) - 1 DVD ISO
SQL Server 2005 Developer Edition - 64-bit Extended - 2x CD ISO
SQL Server 2005 Developer Edition - 32-bit - 2x CD ISO
The desktop is running 64-bit OS, so I definitely want to install 64-bit version. However, I am not sure what this "Extended" version available on CD-s is. Is this the only 64-bit version in existence? Or are there 2 different 64-bit versions
- "Extended" and "Non-Extended" (with non-extended possibly available on DVD - I haven't downloaded any images yet)?SQL Server 2005 Developer Edition - DVD (English) - 1 DVD ISO
SQL Server 2005 Developer Edition - 64-bit Extended - 2x CD ISO
SQL Server 2005 Developer Edition - 32-bit - 2x CD ISO
The desktop is running 64-bit OS, so I definitely want to install 64-bit version. However, I am not sure what this "Extended" version available on CD-s is. Is this the only 64-bit version in existence? Or are there 2 different 64-bit versions - "Extended"
and "Non-Extended" (with non-extended possibly available on DVD - I haven't downloaded any images yet)?
SQL server 2005 is outdated so sorry if my answer is not to the point . First DVD version seems to me like installable which has both database engine and client tools present in it for installation
For second, SQL server 2005 installable was available in 2 CD's 1st CD was to install database engine/SSIS/SSAS/ SSRS features while second CD was to install specifically clint tools,books online legacy support . Its not possible to comment further without
looking at contents but I guess you can use 2nd one. CD 1 would have one part of installable and CD 2 would have second
And of course 3rd one is 32 bit of 2nd one.
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
My TechNet Wiki Articles -
High CPU utilization with SQL Server 2005
Our company recently combined our DBs into one SQL 2005 Server.
Dell Power Edge 1800 with 3.00 GHz Xeon Processor 800 FSB, 1 GB of RAM
Dell Power Edge 1600 with 2.80 GHz Xeon Processor 533 FSB, 1 GB of RAM
Combined into one:
Dell Power Edge 2950 Dual Core 1.6 GHz Xeon Woodcrest Processor, 4 GB of RAM
However, the CPU utilization on this new server is maintaining at about 90% with 3.82 GB of RAM used as well. It's a Windows Server 2003 R2 x64 edition running SQL Server 2005 SP2 x64. I have searched around Microsoft's website for any information that could be of help to me, but I was unable to locate anything. I was hoping that someone could provide some insight as to why this might be occuring. Or if this is a known issue.
Thanks,
PeterHello!
Here are some steps to take after upgrading your SQL Server from 2K to 2K5. (This quote is from BOL)
After upgrading the Database Engine to SQL Server 2005, complete the following tasks:
Register your servers - Upgrade removes registry settings for the previous SQL Server instance. After upgrading, you must reregister your servers.
Repopulate full-text catalogs - The upgrade process marks your databases as full-text disabled. Catalogs must be repopulated, but this operation is not run automatically by Setup because it can be time-consuming. As this operation enhances the performance of your SQL Server 2005 installation, administrators should plan to repopulate full-text catalogs at a convenient time.
Update statistics - To help optimize query performance, we recommend that you update statistics on all databases following upgrade. Use the sp_updatestats stored procedure to update statistics in user-defined tables in SQL Server 2005 databases.
Update usage counters - In earlier versions of SQL Server, the values for the table and index row counts and page counts can become incorrect. To correct any invalid row or page counts, we recommend that you run DBCC UPDATEUSAGE on all databases following upgrade.
Configure your new SQL Server installation - To reduce the attackable surface area of a system, SQL Server 2005 selectively installs and activates key services and features. For more information on how to activate SQL Server 2005 features, see SQL Server Surface Area Configuration.
Source:
How to: Upgrade to SQL Server 2005 (Setup)
http://msdn2.microsoft.com/en-us/library/ms144267.aspx -
How much Memory should be allocated to SQL Server 2005
Hi,
I have a SQL Server 2005 installation on a server having 64GBof RAM.
SQL server is allocated 57GB of the available RAM.
Could you please tell me what would be the ideal RAM allocation for my scenario. is the one that is set now, fine.
How much RAM should be left for the OS and other processes to run?
I have around 8 databases on the server and the cumulative size of all the databases in about 800GB, these are highly used servers, used for a public domain.Umesh,
Saeid and Uri has already given you good articles to refer to please read them. Reg SQL Server utilization I am sure you are referring to task manager which is always not correct place to look for memory utilization. Below link has query which will give
you SQL Server memory utilization
http://blogs.msdn.com/b/sqlsakthi/archive/2011/02/28/t-sql-script-to-monitor-memory-usage-by-sql-server-instance.aspx
Article provided by Uri will give you not absolute value but almost correct value, but since you asked absolute value you need to look at performance counter to reach at correct memory utilization. If you refer to section 'Does my SQL server has low memory'
in article which Saeid gave you will find list of counters to monitor for memory utilization use the counters to reah absolute value.
>>OK, Can high RAM utilization by sql server cause the OS to restart by any chance.
IMO its not possible I have never seen SQL server being cause for OS shutdown. SQL Server works in non preemptive mode and will yield memory to OS when required. One possibility is when SQL server has locked pages in memory(LPIM) and some rouge process
or driver starts using memory from OS heavily and since SQL server memory is locked( due to LPIM privilege) it cannot trim heavily resulting in OS to terminate but this is not because of SQL server but because of bad drivers and processes leaking
memory on OS.
SQL server using memory is normal behavior
>>This question seems vague, but I had to ask this, because my server restarts abruptly and I don't get valid reasons in the Logs for that matter.
Does SQL server starts abruptly or windows OS ? Please look at event viewer for more details and SQL server logs. Is your SQL Server 2005 patched to SP4
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
My TechNet Wiki Articles -
Error 1406 while installing SQL server 2005 on windows 2003 64 bit standard
Hi Gurus,
When I am trying to install SQL SERVER 2005 on Windows Serevr 2005 i get the error code 1406
I tried using the script sql4sap.vbs. and tried to set the named instance.
please suggest
Please find the contents of the Summary.txt
Microsoft SQL Server 2005 9.00.1399.06
==============================
OS Version : Microsoft Windows Server 2003 family, Standard Edition Service Pack 2 (Build 3790)
Time : Mon Apr 14 14:51:07 2008
Machine : UKSAPTEST02
Product : .NET Framework 2.0
Product Version : 2.0.50727
Install : Failed
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_UKSAPTEST02_.NET Framework 2.0.log
Last Action : InstallFinalize
Error String :Could not write value to key \Software\Classes\.appref-ms
Error Number : 1406
UKSAPTEST02 : There was an unexpected failure during the setup wizard. You may review the setup logs and/or click the help button for more information.
SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt.
Time : Mon Apr 14 14:52:26 2008
List of log files:
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_UKSAPTEST02_Core.log
Many thanks
Sreeram
Edited by: sreeram kaki on Apr 14, 2008 6:12 PMHi Clas,
Thanks for the valuable suggestions,
I tried to install the database (sql server 2005) using the local admin password on another server which do not have the antivirus installed. I started the installation at 3:15 PM today and the installation is still in progerss
please see the log below from Summary.txt.
Microsoft SQL Server 2005 9.00.1399.06
==============================
OS Version : Microsoft Windows Server 2003 family, Standard Edition Service Pack 2 (Build 3790)
Time : Tue Apr 15 15:04:28 2008
Machine : UKSAPTEST01
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_UKSAPTEST01_SQLSupport_1.log
Machine : UKSAPTEST01
Product : Microsoft SQL Server Native Client
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_UKSAPTEST01_SQLNCLI_1.log
Machine : UKSAPTEST01
Product : Microsoft SQL Server VSS Writer
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_UKSAPTEST01_SqlWriter_1.log
Machine : UKSAPTEST01
Product : MSXML 6.0 Parser
Product Version : 6.00.3883.8
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_UKSAPTEST01_MSXML6_1.log
Machine : UKSAPTEST01
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_UKSAPTEST01_SQLSupport_2.log
Machine : UKSAPTEST01
Product : Microsoft SQL Server Native Client
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_UKSAPTEST01_SQLNCLI_2.log
Machine : UKSAPTEST01
Product : Microsoft SQL Server 2005 Books Online (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_UKSAPTEST01_BOL_1.log
Machine : UKSAPTEST01
Product : MSXML 6.0 Parser
Product Version : 6.00.3883.8
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_UKSAPTEST01_MSXML6_2.log
Also see the last few lines of the log file
SQLSetup0001_UKSAPTEST01_SQL.log
Action start 17:10:43: Rollback_sqlGroupMember.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B.
MSI (s) (C0!50) [17:10:43:815]: PROPERTY CHANGE: Deleting Rollback_sqlGroupMember.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B property. Its current value is '1 0 0 Installing Local Groups 50000 SQLServer2005MSFTEUser$UKSAPTEST01$RDE NT AUTHORITY\SYSTEM '.
Action ended 17:10:43: Rollback_sqlGroupMember.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B. Return value 1.
<EndFunc Name='ScheduleActionX' Return='0' GetLastError='0'>
<Func Name='ScheduleActionX'>
<Func Name='SetCAContext'>
MSI (s) (C0!50) [17:10:43:815]: PROPERTY CHANGE: Adding Do_sqlGroupMember.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B property. Its value is '1 1 0 Installing Local Groups 50000 SQLServer2005MSFTEUser$UKSAPTEST01$RDE NT AUTHORITY\SYSTEM '.
MSI (s) (C0!50) [17:10:43:815]: Doing action: Do_sqlGroupMember.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B
<EndFunc Name='SetCAContext' Return='T' GetLastError='0'>
Action start 17:10:43: Do_sqlGroupMember.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B.
MSI (s) (C0!50) [17:10:43:830]: PROPERTY CHANGE: Deleting Do_sqlGroupMember.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B property. Its current value is '1 1 0 Installing Local Groups 50000 SQLServer2005MSFTEUser$UKSAPTEST01$RDE NT AUTHORITY\SYSTEM '.
Action ended 17:10:43: Do_sqlGroupMember.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B. Return value 1.
<EndFunc Name='ScheduleActionX' Return='0' GetLastError='0'>
<EndFunc Name='Write_sqlGroupMember' Return='0' GetLastError='0'>
PerfTime Stop: Write_sqlGroupMember : Tue Apr 15 17:10:43 2008
<EndFunc Name='LaunchFunction' Return='0' GetLastError='0'>
MSI (s) (C0:F0) [17:10:43:830]: Doing action: Write_sqlUserSecurity.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B
Action ended 17:10:43: Write_sqlGroupMember.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B. Return value 1.
MSI (s) (C0:50) [17:10:43:830]: Invoking remote custom action. DLL: C:\WINDOWS.0\Installer\MSI1D8.tmp, Entrypoint: Write_sqlUserSecurity
Action start 17:10:43: Write_sqlUserSecurity.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B.
<Func Name='LaunchFunction'>
Function=Write_sqlUserSecurity
<Func Name='SetCAContext'>
<EndFunc Name='SetCAContext' Return='T' GetLastError='0'>
Doing Action: Write_sqlUserSecurity
PerfTime Start: Write_sqlUserSecurity : Tue Apr 15 17:10:43 2008
<Func Name='Write_sqlUserSecurity'>
<Func Name='ScheduleActionX'>
<Func Name='SetCAContext'>
MSI (s) (C0!34) [17:10:43:924]: PROPERTY CHANGE: Adding Do_sqlUserSecurity.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B property. Its value is '0 1 0 Setting User Security 50000 SQLServer2005SQLBrowserUser$UKSAPTEST01 SeServiceLogonRight SQLServer2005SQLAgentUser$UKSAPTEST01$RDE SeServiceLogonRight SQLServer2005SQLAgentUser$UKSAPTEST01$RDE SeBatchLogonRight SQLServer2005SQLAgentUser$UKSAPTEST01$RDE SeAssignPrimaryTokenPrivilege SQLServer2005SQLAgentUser$UKSAPTEST01$RDE SeChangeNotifyPrivilege SQLServer2005SQLAgentUser$UKSAPTEST01$RDE SeIncreaseQuotaPrivilege SQLServer2005MSSQLUser$UKSAPTEST01$RDE SeServiceLogonRight SQLServer2005MSSQLUser$UKSAPTEST01$RDE SeBatchLogonRight SQLServer2005MSSQLUser$UKSAPTEST01$RDE SeAssignPrimaryTokenPrivilege SQLServer2005MSSQLUser$UKSAPTEST01$RDE SeChangeNotifyPrivilege SQLServer2005MSSQLUser$UKSAPTEST01$RDE SeIncreaseQuotaPrivilege SQLServer2005MSFTEUser$UKSAPTEST01$RDE SeServiceLogonRight SQLServer2005MSFTEUser$UKSAPTEST01$RDE SeBatchLogonRight SQLServer2005MSFTEUser$UKSAPTEST01$RDE SeAssignPrimaryTokenPrivilege SQLServer2005MSFTEUser$UKSAPTEST01$RDE SeChan
MSI (s) (C0!34) [17:10:43:924]: Doing action: Do_sqlUserSecurity.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B
<EndFunc Name='SetCAContext' Return='T' GetLastError='0'>
Action start 17:10:43: Do_sqlUserSecurity.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B.
MSI (s) (C0!34) [17:10:43:924]: PROPERTY CHANGE: Deleting Do_sqlUserSecurity.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B property. Its current value is '0 1 0 Setting User Security 50000 SQLServer2005SQLBrowserUser$UKSAPTEST01 SeServiceLogonRight SQLServer2005SQLAgentUser$UKSAPTEST01$RDE SeServiceLogonRight SQLServer2005SQLAgentUser$UKSAPTEST01$RDE SeBatchLogonRight SQLServer2005SQLAgentUser$UKSAPTEST01$RDE SeAssignPrimaryTokenPrivilege SQLServer2005SQLAgentUser$UKSAPTEST01$RDE SeChangeNotifyPrivilege SQLServer2005SQLAgentUser$UKSAPTEST01$RDE SeIncreaseQuotaPrivilege SQLServer2005MSSQLUser$UKSAPTEST01$RDE SeServiceLogonRight SQLServer2005MSSQLUser$UKSAPTEST01$RDE SeBatchLogonRight SQLServer2005MSSQLUser$UKSAPTEST01$RDE SeAssignPrimaryTokenPrivilege SQLServer2005MSSQLUser$UKSAPTEST01$RDE SeChangeNotifyPrivilege SQLServer2005MSSQLUser$UKSAPTEST01$RDE SeIncreaseQuotaPrivilege SQLServer2005MSFTEUser$UKSAPTEST01$RDE SeServiceLogonRight SQLServer2005MSFTEUser$UKSAPTEST01$RDE SeBatchLogonRight SQLServer2005MSFTEUser$UKSAPTEST01$RDE SeAssignPrimaryTokenPrivilege SQLServer2005MSFTEUser$UKSAPTEST01$
Action ended 17:10:43: Do_sqlUserSecurity.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B. Return value 1.
<EndFunc Name='ScheduleActionX' Return='0' GetLastError='0'>
<EndFunc Name='Write_sqlUserSecurity' Return='0' GetLastError='0'>
PerfTime Stop: Write_sqlUserSecurity : Tue Apr 15 17:10:43 2008
<EndFunc Name='LaunchFunction' Return='0' GetLastError='0'>
MSI (s) (C0:F0) [17:10:43:940]: Doing action: Write_sqlFileSDDL.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B
Action ended 17:10:43: Write_sqlUserSecurity.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B. Return value 1.
MSI (s) (C0:10) [17:10:43:940]: Invoking remote custom action. DLL: C:\WINDOWS.0\Installer\MSI1D9.tmp, Entrypoint: Write_sqlFileSDDL
Action start 17:10:43: Write_sqlFileSDDL.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B.
<Func Name='LaunchFunction'>
Function=Write_sqlFileSDDL
<Func Name='SetCAContext'>
<EndFunc Name='SetCAContext' Return='T' GetLastError='0'>
Doing Action: Write_sqlFileSDDL
PerfTime Start: Write_sqlFileSDDL : Tue Apr 15 17:10:43 2008
Thanks & Regards,
Sreeram
Edited by: sreeram kaki on Apr 15, 2008 6:45 PM -
I am installing SQL Server 2012 Developer (from ISO image written on DVD), my machine has Windows 7 (Edit: Windows 7 with service pack 1) on it. This machine already has SQL Express and SQL 2008 R2 Express installed in it.
On running 2012 setup it goes fine from Setup Support Rules to Installation Progress. In Installation Progress after some progress installation fails.
Windows show the following components couldn't installed:
Managment Tools Complete Failed. Client Tools Connectivity Failed. Client Tools SDK Failed. Client Tools Backwards Compantibility Failed. Managment Tools Basic Failed. SQL Server Data Tools Failed. Reporting Services -Native Failed. Database Engine
Services Failed. Data Quality Services Failed. full-Text and Semantic Extractins for Search Failed. SQL Server Replication Failed. Integration Services Failed. Analysis Services Failed. SQL Client Connectivity SDK Failed.
In detail for failure of every component it provide these details:
Action required:
Use the following information to resolve the error, and then try the setup process again.
Feature failure reason:
An error occurred for a dependency of the feature causing the setup process for the feature to fail.
In summary log file it provide the following details:
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2068643839
Start time: 2012-07-31 16:23:37
End time: 2012-07-31 16:33:32
Requested action: Install
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for Adv_SSMS: Use the following information to resolve the error, and then try the setup process again.
Next step for Conn: Use the following information to resolve the error, and then try the setup process again.
Next step for SDK: Use the following information to resolve the error, and then try the setup process again.
Next step for BC: Use the following information to resolve the error, and then try the setup process again.
Next step for SSMS: Use the following information to resolve the error, and then try the setup process again.
Next step for BIDS: Use the following information to resolve the error, and then try the setup process again.
Next step for RS: Use the following information to resolve the error, and then try the setup process again.
Next step for SQLEngine: Use the following information to resolve the error, and then try the setup process again.
Next step for DQ: Use the following information to resolve the error, and then try the setup process again.
Next step for FullText: Use the following information to resolve the error, and then try the setup process again.
Next step for Replication: Use the following information to resolve the error, and then try the setup process again.
Next step for IS: Use the following information to resolve the error, and then try the setup process again.
Next step for AS: Use the following information to resolve the error, and then try the setup process again.
Next step for SNAC_SDK: Use the following information to resolve the error, and then try the setup process again.
Machine Properties:
Machine name: Haansi-PC
Machine processor count: 4
OS version: Windows 7
OS service pack: Service Pack 1
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID
Feature Language
Edition Version Clustered
SQL Server 2005 SQLEXPRESS MSSQL.1
Database Engine Services 1033 Express Edition
9.4.5000 No
SQL Server 2005 SQLEXPRESS MSSQL.1
SQL Server Replication 1033 Express Edition
9.4.5000 No
SQL Server 2005 SQLEXPRESS MSSQL.1
SharedTools 1033
Express Edition 9.4.5000 No
SQL Server 2005
Tools 1033
Express Edition 9.4.5000 No
SQL Server 2005
ToolsClient 1033
Express Edition 9.4.5000 No
SQL Server 2005
ToolsClient\Connectivity 1033 Express Edition
9.4.5000 No
SQL Server 2008 R2 SQLSERVER08EXPR2 MSSQL10_50.SQLSERVER08EXPR2 Database Engine Services 1033
Express Edition 10.50.1617.0 No
SQL Server 2008 R2 SQLSERVER08EXPR2 MSSQL10_50.SQLSERVER08EXPR2 SQL Server Replication 1033
Express Edition 10.50.1617.0 No
SQL Server 2008 R2
Management Tools - Basic 1033 Express Edition
10.50.1617.0 No
SQL Server 2012
LocalDB 1033
Express Edition 11.0.2318.0 No
SQL Server 2012
Reporting Services - SharePoint
11.0.2100.60 No
Package properties:
Description: Microsoft SQL Server 2012
ProductName: SQL Server 2012
Type: RTM
Version: 11
SPLevel: 0
Installation location: F:\x64\setup\
Installation edition: Developer
Product Update Status:
None discovered.
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: false
AGTSVCACCOUNT: NT Service\SQLAgent$SS2012
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Manual
ASBACKUPDIR: C:\Program Files\Microsoft SQL Server\MSAS11.SS2012\OLAP\Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: C:\Program Files\Microsoft SQL Server\MSAS11.SS2012\OLAP\Config
ASDATADIR: C:\Program Files\Microsoft SQL Server\MSAS11.SS2012\OLAP\Data
ASLOGDIR: C:\Program Files\Microsoft SQL Server\MSAS11.SS2012\OLAP\Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: TABULAR
ASSVCACCOUNT: NT Service\MSOLAP$SS2012
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Manual
ASSYSADMINACCOUNTS: PC\Haansi
ASTEMPDIR: C:\Program Files\Microsoft SQL Server\MSAS11.SS2012\OLAP\Temp
BROWSERSVCSTARTUPTYPE: Automatic
CLTCTLRNAME: <empty>
CLTRESULTDIR: <empty>
CLTSTARTUPTYPE: 0
CLTSVCACCOUNT: <empty>
CLTSVCPASSWORD: <empty>
CLTWORKINGDIR: <empty>
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20120731_161013\ConfigurationFile.ini
CTLRSTARTUPTYPE: 0
CTLRSVCACCOUNT: <empty>
CTLRSVCPASSWORD: <empty>
CTLRUSERS: <empty>
ENABLERANU: false
ENU: true
ERRORREPORTING: false
FEATURES: SQLENGINE, REPLICATION, FULLTEXT, DQ, AS, RS, BIDS, CONN, IS, BC, SDK, SSMS, ADV_SSMS, SNAC_SDK
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: NT Service\MSSQLFDLauncher$SS2012
FTSVCPASSWORD: <empty>
HELP: false
INDICATEPROGRESS: false
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: SS2012
INSTANCENAME: SS2012
ISSVCACCOUNT: NT Service\MsDtsServer110
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: <empty>
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: DefaultSharePointMode
RSSVCACCOUNT: NT Service\ReportServer$SS2012
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Manual
SAPWD: <empty>
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: NT Service\MSSQL$SS2012
SQLSVCPASSWORD: <empty>
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: Haansi-PC\Haansi
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: false
TCPENABLED: 0
UIMODE: Normal
UpdateEnabled: true
UpdateSource: MU
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20120731_161013\ConfigurationFile.ini
Detailed results:
Feature: Management Tools - Complete
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: Client Tools Connectivity
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: Client Tools SDK
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: Client Tools Backwards Compatibility
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: Management Tools - Basic
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: SQL Server Data Tools
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: Reporting Services - Native
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: Database Engine Services
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: Data Quality Services
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: Full-Text and Semantic Extractions for Search
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: SQL Server Replication
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: Integration Services
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: Analysis Services
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: SQL Client Connectivity SDK
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20120731_161013\SystemConfigurationCheck_Report.htmPlease help.
I did what you suggested, but, still got error message to install SQL server data tools: Here is the log.
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2068037632
Start time: 2014-09-29 15:05:38
End time: 2014-09-29 15:15:55
Requested action: Install
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for SSDTBI_VS2012: Use the following information to resolve the error, and then try the setup process again.
Machine Properties:
Machine name: MSBI
Machine processor count: 4
OS version: Future Windows Version
OS service pack:
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 32 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature
Language Edition Version Clustered Configured
SQL Server 2008 Management Tools - Basic
1033 Express Edition 10.0.1600.22 No Yes
SQL Server 2012 MSSQLSERVER MSSQL11.MSSQLSERVER Database Engine Services 1033
Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 MSSQLSERVER MSSQL11.MSSQLSERVER SQL Server Replication 1033
Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 MSSQLSERVER MSSQL11.MSSQLSERVER Full-Text and Semantic Extractions for Search 1033
Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 MSSQLSERVER MSSQL11.MSSQLSERVER Data Quality Services 1033
Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 MSSQLSERVER MSAS11.MSSQLSERVER Analysis Services 1033
Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 MSSQLSERVER MSRS11.MSSQLSERVER Reporting Services - Native 1033
Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 Management Tools - Basic
1033 Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 Management Tools - Complete
1033 Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 Client Tools Connectivity
1033 Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 Client Tools Backwards Compatibility
1033 Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 Client Tools SDK
1033 Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 SQL Server Data Tools
1033 Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 Integration Services
1033 Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 Reporting Services - SharePoint
11.0.2100.60 No Yes
Package properties:
Description: Microsoft SQL Server 2012 Service Pack 1
ProductName: SQL Server 2012
Type: RTM
Version: 11
Installation location: C:\9f7a58aa5d6d76ffe6be968a4ad339f5\x86\setup\
Installation edition: Express
Slipstream: True
SP Level 1
Patch Level: 11.1.3128.0
Product Update Status:
Success: KB 2674319, KB 2793634
Product Updates Selected for Installation:
Title: Service Pack 1
Knowledge Based Article: KB 2674319
Version: 11.1.3000.0
Architecture: x86
Language: 1033
Title: SQL Server 2012 SP1 GDR Product Update
Knowledge Based Article: KB 2793634
Version: 11.1.3128.0
Architecture: x86
Language: All
Update Source: MU
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: true
AGTSVCACCOUNT: <empty>
AGTSVCPASSWORD: <empty>
AGTSVCSTARTUPTYPE: Manual
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: MULTIDIMENSIONAL
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Disabled
CLTCTLRNAME: <empty>
CLTRESULTDIR: <empty>
CLTSTARTUPTYPE: 0
CLTSVCACCOUNT: <empty>
CLTSVCPASSWORD: <empty>
CLTWORKINGDIR: <empty>
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE:
CTLRSTARTUPTYPE: 0
CTLRSVCACCOUNT: <empty>
CTLRSVCPASSWORD: <empty>
CTLRUSERS: <empty>
ENABLERANU: false
ENU: true
ERRORREPORTING: true
FEATURES: SSDTBI_VS2012, SNAC_SDK
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: <empty>
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTSQLSERVERLICENSETERMS: true
INDICATEPROGRESS: false
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTANCEID: <empty>
INSTANCENAME: <empty>
ISSVCACCOUNT: NT AUTHORITY\Network Service
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: AllFeatures_WithDefaults
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: DefaultSharePointMode
RSSVCACCOUNT: <empty>
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: <empty>
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: <empty>
SQLSVCPASSWORD: <empty>
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: <empty>
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: true
TCPENABLED: 0
UIMODE: AutoAdvance
UpdateEnabled: true
UpdateSource: MU
X86: false
Configuration file: C:\Program Files (x86)\Microsoft SQL Server\110\Setup Bootstrap\Log\20140929_150412\ConfigurationFile.ini
Detailed results:
Feature: SQL Server Data Tools - Business Intelligence for Visual Studio 2012
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: Microsoft Visual Studio Tools for Applications 2012
Component error code: 0x80044000
Component log file: C:\Program Files (x86)\Microsoft SQL Server\110\Setup Bootstrap\Log\20140929_150412\VSTA2012_LangsSupport_Cpu32_1.log
Error description: VS Shell 2012 installation has failed with exit code -2147205120.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3436.0&EvtType=VSTA2012_LangsSupport%40Install%400x-2147205120
Feature: SQL Client Connectivity
Status: Passed
Feature: SQL Client Connectivity SDK
Status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files (x86)\Microsoft SQL Server\110\Setup Bootstrap\Log\20140929_150412\SystemConfigurationCheck_Report.htm -
SQL Server Error when tryingt to install the CMS DB on SQL Server 2005 x64
I am trying to install BOEXI R3 on w2k3 64-bit OS in a SQL Server 2005 x64 database, I am currently at the installation step where i Specify an exisiting CMS database. I created a System DSN and tested it, and it was successful. So when I got to the screen where I select my datasource I had to check use trusted connection because the datasource would not show up when Use DSN created by WOW64 option was checked. From there I could select the database I created. Oh yeah, I also made the application server local system account part of my DB admins group so it has full access to the database yet when I click next to connect I get a CMS Database Error: STU000226. here is what I have in my log:
ThreadID Message
(Thu Apr 23 20:57:46 2009) 3024 3028 trace message: findDFA_LLR: (CmdLineDir) C:Documents and SettingsgsdadminDesktopBOEXI and BSM AnalyticsBOEXI R3 Full Version from SAPpackagedbcheck
sqlrule.llr
(Thu Apr 23 20:57:46 2009) 3024 3028 trace message: Loading: database subsystem only
(Thu Apr 23 20:57:46 2009) 3024 3028 trace message: loading libary succeeded
(Thu Apr 23 20:57:46 2009) 3024 3028 trace message: DatabaseSubsystem::Init()
(Thu Apr 23 20:57:46 2009) 3024 3028 (.wireobinit.cpp:96): trace message: Creating the shared CWireObject::PropertyNameMap
(Thu Apr 23 20:57:46 2009) 3024 3028 (.wireobinit.cpp:118): trace message: Setting static property map
(Thu Apr 23 20:57:46 2009) 3024 3028 (.wireobinit.cpp:125): trace message: CWireObject::InitializeStaticPropertyMap() - reference count: 1
(Thu Apr 23 20:57:46 2009) 3024 3028 trace message: initializing subsystem succeeded
(Thu Apr 23 20:57:46 2009) 3024 3028 trace message: Loading: done loading subsystem - database subsystem only
(Thu Apr 23 20:57:46 2009) 3024 3028 trace message: DatabaseSubsystem::Connect()
(Thu Apr 23 20:57:46 2009) 3024 3028 (.DBConnectionManager.cpp:802): trace message: DBConnectionManager - Setting total target number of connections for pool 0 to 1.
(Thu Apr 23 20:57:46 2009) 3024 3028 (.SQLServerDatabase.cpp:119): trace message: SQLServer error found: ErrorMessage( (Microsoft)[ODBC Driver Manager] Data source name not found and no default driver specified), ErrorCode(0)
(Thu Apr 23 20:57:46 2009) 3024 3028 (.dbutils.cpp:820): trace message: Caught DatabaseSubystem Error: BusinessObjects Enterprise CMS: Unable to connect to the CMS system database "BOEXI_CMS". Reason: (Microsoft)[ODBC Driver Manager] Data source name not found and no default driver specified
(Thu Apr 23 20:57:46 2009) 3024 3028 trace message: DatabaseSubsystem::Shutdown()
(Thu Apr 23 20:57:46 2009) 3024 3028 (.wireobinit.cpp:175): trace message: CWireObject::TerminateStaticPropertyMap() - reference count: 1
(Thu Apr 23 20:57:46 2009) 3024 3028 (.wireobinit.cpp:182): trace message: Releasing
static property map
How do I get past this?The workaround was, I installed the SQL Server Client tools and created a System DataSource and then had to create a user DataSource (it is a quirk in the installer I guess) to get past this point in the installation. Now I have an even bigger problem. Everything but the CMS installed and the installer hung at the "Configuring the CMS" part. The installation finished but when I tried to log into the Central managment console I got this error:
Error: Server GSD-RRPT-RDC:6400 not found or server may be down (FWM 01003) null
I looked at the forums for the cause of this error and came to the conclusion that BOEXI does not support an installation on SQL Server 2005 when using Integrated Authentication to the SQL Server. See the engineers here disabled SQL Authentication for the SQL Server and will not allow it.
Is this true? Or is there a workaround to install the CMS using Integrated Authentication in the DataSource ?
Thanks.
Maybe you are looking for
-
Scenario: With the release of Windows 10 Technical Preview (build 9926), some users may encounter an error message of “The account is not authorized to login from this station” when trying to access remote files saved in NAS storage. In addition, the
-
I normally do "defragment" in my PC. But how can I do "defragment" in my Macbook?
-
11g pivot query syntax question
I searched the forums and I have seen questions similiar to the one I am asking, but its not the exact same issue. I need 3 fields in my 'for' clause. I get 'column ambiguously defined. I think I get this error for a different reason that other peopl
-
Changes in fields of SC trigger Email back to Requestor
Hello! All I am using n-badi workflow for shopping cart. There is no start condition for this workflow. When a approver makes a change in price , a e-mail triggers back to requestor to ACCEPT CHANGES OR REJECT CHANGES. When an approver makes a change
-
Adding Two more Wireless bridges - Etherchannel
Two facilites are connected via wireless bridge(AIR-BR1410A-E-K9). we wanted to add wireless bridge at each facility to increase the bandwidth. So we will have two wireless bridge at each facility connected wirelessly. and we wanted to achieve it by