After Install, Running Sqlcmd -S ServerInstance Fails
Jan 23, 2007
I'm trying to figure out how to set up SQL Express so I can start learning SQL. I've installed SQL Express, but when I type "sqlcmd -S ServerSQLExpress," I receive the following error:Microsoft Windows XP [Version 5.1.2600](C) Copyright 1985-2001 Microsoft Corp.C:Documents and SettingsUsername>sqlcmd -S ServerSQLExpressHResult 0xFFFFFFFF, Level 16, State 1SQL Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF].Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections..Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.
I'm attempting to install sql for a BCM 2007 installation, and I'm using this document: http://www.microsoft.com/downloads/details.aspx?familyid=f24267ee-9ad5-4be5-b888-c9a50ae395ca&displaylang=en
Now, I'm trying to do this on Windows 2003 Standard server, which may be the problem, but perhaps not? Anyway, the command I'm attempting to run is: sqlcmd €“S .\%INSTANCENAME% €“E €“Q €œexec sp_grantlogin [%DOMAIN%\%USER%]; grant create database to [%DOMAIN%\%USER%]€?
which is basic enough (and I did replace the %%'s with the correct info) but I'm getting this error back:
Sqlcmd: '-S': Unknown Option. Enter '-?' for help.
Any ideas???
edit: I did just notice this from the sql express readme, so I may try reinstalling... advice would still be appreciated!
3.10 Installing SQL Server Express on a Windows Domain Controller Security Note: We recommend against running SQL Server Express on a domain controller. It is possible to install SQL Server Express on a Windows domain controller; however, it cannot run on a Windows Server 2003 domain controller as Local Service or Network Service. SQL Server service accounts should run as Windows domain user accounts. It is also possible to install SQL Server service accounts to run as Local System, but this option is not recommended. Do not change the role of the server after you install SQL Server Express. For example, if you install SQL Server Express on a member server, do not use the Dcpromo tool to promote the server to a domain controller. Or, if you install SQL Server Express on a domain controller, do not use Dcpromo to demote the server to a member server. Changing the role of a server after you install SQL Server Express can result in loss of functionality and is not supported.
I have SQL Server 2000 client installed in my machine and I need to call stored procedures thru sqlcmd utility. When I tried using this utility, I got an error message from command prompt sqlcmd command does not exist.
I have osql utility in my client version, but i need to have sqlcmd utility.
Please advice how do I install sqlcmd.exe in my SQL Server client?
Log Location: C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQL9_Hotfix_KB921896_sqlrun_sql.msp.log MSP Error: 29537 SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]Cannot find the object 'dm_exec_query_resource_semaphores', because it does not exist or you do not have permission.. To continue, correct the problem, and then run SQL Server Setup again.
I tried to search internet, however, I couldn't get solution.
My SQL server 2005 is standard version, OS Windows server 2003 sp2, I am using Administrator account to install it.
We are trying to install the Standard Edition of SQL Server 2005. We already have SQL Express installed. Standard won't install and Express won't uninstall.
We have tried every suggestion we can find and some we made up. When we try to install Standard, we get to the bit where you choose what you want to install and the only thing available is workstation components.
There are so many cases of this on the Internat that I can't believe MS have not solved the issue. And I am stunned that they want to charge us more money to talk to us about how to fix something we just paid them an arm and a leg for!
What do I need to tell you to get some idea of where to go next with this?
I can't find this anywhere in the thousands of objects in SSIS. So I thought I would ask.
I have a situtation where I want to retrieve the serverinstance name of the SSIS job is running on. I have multiple servers and instances and I want to send emails like "Failed see serverinstance - job name".
Hello, I have a DTS job that retrieves data from a different server. When I manually run the DTS job, it executes fine, but when I run it from an SQL job it fails regardless of the owner I use to run the SQL job under. I ran the same DTS package from another computer which has SQL client installed and it ran fine. Does anyone know what could be the reason for failure when running the DTS job from the SQL job from the server?
Hi groupI want to make a new serverinstance, but based on some old files from aprevious instance I once had from a SQL I scrapped.I only know how to use the SQL Server enterprise manager console, and Ihaven't found any tools in there to do that.Any suggestion will be more than welcome.Adrian
I am working on setting up our new SQL Server 2005 servers. One ofthem will eventually be our Replication Distributor. However when Iattempt to set this up within the wizard, I get the following error:------------------------------TITLE: New Publication Wizard------------------------------SQL Server could not configure 'ServerInstance' as a Distributor.------------------------------ADDITIONAL INFORMATION:Property LoginSecure cannot be changed or read after a connectionstring has been set. (Microsoft.SqlServer.ConnectionInfo)------------------------------BUTTONS: OK------------------------------In the "Specify the Domain or Machine account under which the Snap ShotAgent will run" page, I designate a Windows Auth. domain user; The sameuser that is used to start SQL Service. Any idea as to why I amgetting this error?
The sp2 fails on database services and analysis services, but completes everything else.
Any suggestions would be appreciated.
Andy
Below is an excerpt from the log: 05/18/2007 10:41:13.620 Copy Engine: Creating MSP install log file at: C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQL9_Hotfix_KB921896_sqlrun_sql.msp.log 05/18/2007 10:41:13.620 Registry: Opened registry key "SoftwarePoliciesMicrosoftWindowsInstaller" 05/18/2007 10:41:13.620 Registry: Cannot read registry key value "Debug" 05/18/2007 10:41:25.041 MSP Error: 29528 The setup has encountered an unexpected error while Setting Internal Properties. The error is: Fatal error during installation.
I'm having trouble installing SQL Server 2005 Express SP2 on WinXP Home SP2. I've had no troubles installing on another WinXP Professional machine.
As it installs, the setup progress shows that following componenets failed : MSXML6, SQL Server Database Services, and Workstation Components, Books Online.
The other three components succeeded. When I click on Finish, it crashes with the error message "Microsoft SQL Server 2005 Setup was unable to install on your computer", with the option to send an error report which I have done.
Here is the Summary Log and the MSXML6 log. If you want other logs, please specify which ones.
Summary.txt
Microsoft SQL Server 2005 9.00.3042.00 ============================== OS Version : Microsoft Windows XP Home Edition Service Pack 2 (Build 2600) Time : Sun Apr 13 12:12:25 2008
Machine : DELL-PC Product : Microsoft SQL Server Setup Support Files (English) Product Version : 9.00.3042.00 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_DELL-PC_SQLSupport_1.log -------------------------------------------------------------------------------- Machine : DELL-PC Product : Microsoft SQL Server Native Client Product Version : 9.00.3042.00 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_DELL-PC_SQLNCLI_1.log -------------------------------------------------------------------------------- Machine : DELL-PC Product : Microsoft SQL Server VSS Writer Product Version : 9.00.3042.00 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_DELL-PC_SqlWriter_1.log -------------------------------------------------------------------------------- Machine : DELL-PC Product : Microsoft SQL Server Setup Support Files (English) Product Version : 9.00.3042.00 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_DELL-PC_SQLSupport_2.log -------------------------------------------------------------------------------- Machine : DELL-PC Product : Microsoft SQL Server Native Client Product Version : 9.00.3042.00 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_DELL-PC_SQLNCLI_2.log -------------------------------------------------------------------------------- SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%Microsoft SQL Server90Setup BootstrapLOGSummary.txt.
Subject says it all; I need to install IS, but the installer says v.2047 of IS is already installed; it it NOT installed. When I go to add/remove programs, under the Sql Server 2005, it allows me to try to install IS, but that also fails, as no components are found for installation. This is SS dev edition, W2003.
I can uninstall SS2005 and start over, but is there a quicker way to fix this?
I was trying to install the MSDE 2000 from the Office XP CD in Windows XP Pro. In the middle of the installation, it rolls back, does not give any message and the installation fails. :confused: What could be the problem? Please help me with this
I am trying to build a VB6.0 application with the msde as back end
I'm trying to install SQL into a new cluster. The cluster service is up and running fine. I can even fail it from Node 1 to Node 2 with no problem.
However, when I try to install SQL, I get a screen that tells me that SQL is performing required operations on the cluster nodes...this may take a few minutes.
After hanging on that message for a looong time, SQL comes up with a generic message that the install failed and that SQL is cleaning up. Then, nothing. No error message, nothing that I can track down.
Some system information: Node 1. Dell PE2650, 2x 2.8 GHz, 2 GB RAM - Windows 2000 Advanced Server - Dell Perc3/DC RAID/SCSI Controller - Dell Perc3/DI Integrated RAID Controller
Shared Storage. Dell PV220 - Q: Quorum (1 GB) - S: Data (136 GB) - T: Logs (20 GB)
Additional Notes: 1. I am using a checklist from Dell and another from MS. 2. I have also downloaded and read the checklist from sql-server-performance.com. 3. I have ensured that the comclust.exe was run on both nodes prior to starting the SQL installation 4. I am using SQL Enterprise Edition. We used the same CD to install a cluster server two weeks ago.
Questions: 1. Where can I find an installation error log that might point more specifically to where the problem might be? 2. Any thoughts on what the problem might be? 3. Anyone ever experience something similar?
The installation of MSDE fails and I dont find any solution to get itwork. If I start the setup than a windows with the time bar appears andsays it will take 1 minute. After nearly 1 minute it closes the windowand gives no additional information. But I see that it generates firstall the directories and files in c:Programme but after the setup is endeverything is deleted. Nearly everything , I see a service"MSSQLServerADHelper" is still installed.Must everytime delete it via regedit.I am using WindowsXP SP1 with MDAC 2.8I get this at the end of the generated protokollafter I start setup with"setup SAPWD="mypasswort" SECURITYMODE=SQL /L*v D:/MSDELog.log"Property(C): StartupFolder = C:Dokumente und EinstellungenAllUsersStartmenüProgrammeAutostartProperty(C): ProgramMenuFolder = C:Dokumente und EinstellungenAllUsersStartmenüProgrammeProperty(C): StartMenuFolder = C:Dokumente und EinstellungenAllUsersStartmenüProperty(C): DesktopFolder = C:Dokumente und EinstellungenAllUsersDesktopProperty(C): FontsFolder = C:WINDOWSFontsProperty(C): GPTSupport = 1Property(C): OLEAdvtSupport = 1Property(C): ShellAdvtSupport = 1Property(C): Intel = 6Property(C): PhysicalMemory = 448Property(C): VirtualMemory = 805Property(C): AdminUser = 1Property(C): LogonUser = BILOAGAProperty(C): UserSID = S-1-5-21-1606980848-1563985344-1202660629-1003Property(C): UserLanguageID = 1031Property(C): ComputerName = JUSTLERProperty(C): SystemLanguageID = 1031Property(C): ScreenX = 1024Property(C): ScreenY = 768Property(C): CaptionHeight = 19Property(C): BorderTop = 1Property(C): BorderSide = 1Property(C): TextHeight = 16Property(C): ColorBits = 16Property(C): TTCSupport = 1Property(C): MsiNetAssemblySupport = 1.1.4322.573Property(C): MsiWin32AssemblySupport = 5.1.2600.1106Property(C): RedirectedDllSupport = 2Property(C): Time = 19:43:01Property(C): Date = 18.12.2003Property(C): Privileged = 1Property(C): USERNAME = BILOAGAProperty(C): COMPANYNAME = xxxProperty(C): DATABASE = C:DOKUME~1BILOAGALOKALE~1Temp5b2b57.msiProperty(C): OriginalDatabase = C:SQL2ksp3installSetupSqlRun01.msiProperty(C): UILevel = 3Property(C): ACTION = INSTALL=== Protokollierung beendet: 18.12.2003 19:43:01 ===MSI (c) (B0:20): Note: 1: 1708MSI (c) (B0:20): Produkt: Microsoft SQL Server Desktop Engine --Installationsvorgang fehlgeschlagen.MSI (c) (B0:20): Grabbed execution mutex.MSI (c) (B0:20): Cleaning up uninstalled install packages, if any existMSI (c) (B0:20): MainEngineThread is returning 1603=== Verbose logging stopped: 18.12.2003 19:43:01 ===It would be super if anyone can help me. Havent find any informationsabout this.*** Sent via Developersdex http://www.developersdex.com ***Don't just participate in USENET...get rewarded for it!
I'm having a hard time installing SQLServer 2005. msxml6 keep on failing. The log looks like this.
Installing: msxml6 on target: GPA-DEMO Error: MsiOpenDatabase failed with 87 Failed to install package This action is only valid for products that are currently installed.
If i try to run the MSXML6.msi on the install disk directly i'm getting a permission error. Any ideas?
On a new install of sqlserver 2005 developer edition (on x86 xp sp2) I tried to install sp2 but before anything happens I get the message:
Unexpected Error Occurred The following unexpected error occurred:
But no error message, and no log created in the hotfix folder. I downloaded the sp2 file again but got the same error.
When I click on OK to this error I get 7 messages about "hotfix.exe has encountered a problem and needs to close"
I downloaded sp1 and installed that fine, but after that I still have the same error with sp2. I tried extracting sp2 and replacing hotfix.exe with the one from sp1, which avoided the error but wouldn't install.
Any ideas on how to resolve this would be appreciated.
I have tried multiple times to install SQL Express on a client's machine (Windows XP), every single time the installation fails with and error message "Sql server could not be started". What else can I do to have this install properly? Please help.
ERRORLOG
2007-09-05 15:44:20.14 Server Microsoft SQL Server 2005 - 9.00.3042.00 (Intel X86) Feb 9 2007 22:47:07 Copyright (c) 1988-2005 Microsoft Corporation Express Edition on Windows NT 5.1 (Build 2600: Service Pack 2) 2007-09-05 15:44:20.14 Server (c) 2005 Microsoft Corporation. 2007-09-05 15:44:20.14 Server All rights reserved. 2007-09-05 15:44:20.14 Server Server process ID is 2492. 2007-09-05 15:44:20.14 Server Authentication mode is MIXED. 2007-09-05 15:44:20.14 Server Logging SQL Server messages in file 'c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLLOGERRORLOG'. 2007-09-05 15:44:20.14 Server This instance of SQL Server last reported using a process ID of 2612 at 9/5/2007 3:44:02 PM (local) 9/5/2007 10:44:02 PM (UTC). This is an informational message only; no user action is required. 2007-09-05 15:44:20.14 Server Registry startup parameters: 2007-09-05 15:44:20.14 Server -d c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLDATAmaster.mdf 2007-09-05 15:44:20.14 Server -e c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLLOGERRORLOG 2007-09-05 15:44:20.14 Server -l c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLDATAmastlog.ldf 2007-09-05 15:44:20.14 Server Command Line Startup Parameters: 2007-09-05 15:44:20.14 Server -m SqlSetup 2007-09-05 15:44:20.14 Server SqlSetup 2007-09-05 15:44:20.14 Server -Q 2007-09-05 15:44:20.14 Server -q SQL_Latin1_General_CP1_CI_AS 2007-09-05 15:44:20.14 Server -T 4022 2007-09-05 15:44:20.14 Server -T 3659 2007-09-05 15:44:20.14 Server -T 3610 2007-09-05 15:44:20.14 Server -T 4010 2007-09-05 15:44:20.17 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required. 2007-09-05 15:44:20.17 Server Detected 1 CPUs. This is an informational message; no user action is required. 2007-09-05 15:44:20.25 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required. 2007-09-05 15:44:20.37 Server Database Mirroring Transport is disabled in the endpoint configuration. 2007-09-05 15:44:20.37 spid5s Warning ****************** 2007-09-05 15:44:20.38 spid5s SQL Server started in single-user mode. This an informational message only. No user action is required. 2007-09-05 15:44:20.38 spid5s Starting up database 'master'. 2007-09-05 15:44:20.63 spid5s 13 transactions rolled forward in database 'master' (1). This is an informational message only. No user action is required. 2007-09-05 15:44:20.75 spid5s 0 transactions rolled back in database 'master' (1). This is an informational message only. No user action is required. 2007-09-05 15:44:20.75 spid5s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required. 2007-09-05 15:44:20.82 spid5s SQL Trace ID 1 was started by login "sa". 2007-09-05 15:44:20.84 spid5s Starting up database 'mssqlsystemresource'. 2007-09-05 15:44:20.93 spid5s The resource database build version is 9.00.3042. This is an informational message only. No user action is required. 2007-09-05 15:44:21.15 spid5s Server name is 'S0022882021'. This is an informational message only. No user action is required. 2007-09-05 15:44:21.16 spid7s Starting up database 'model'. 2007-09-05 15:44:21.29 Server Error: 17190, Severity: 16, State: 1. 2007-09-05 15:44:21.29 Server FallBack certificate initialization failed with error code: 1. 2007-09-05 15:44:21.29 Server Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate. 2007-09-05 15:44:21.29 Server Error: 17182, Severity: 16, State: 1. 2007-09-05 15:44:21.29 Server TDSSNIClient initialization failed with error 0x80092004, status code 0x80. 2007-09-05 15:44:21.29 Server Error: 17182, Severity: 16, State: 1. 2007-09-05 15:44:21.29 Server TDSSNIClient initialization failed with error 0x80092004, status code 0x1. 2007-09-05 15:44:21.30 Server Error: 17826, Severity: 18, State: 3. 2007-09-05 15:44:21.30 Server Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log. 2007-09-05 15:44:21.30 Server Error: 17120, Severity: 16, State: 1. 2007-09-05 15:44:21.30 Server SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
Summary:
Microsoft SQL Server 2005 9.00.3042.00 ============================== OS Version : Microsoft Windows XP Professional Service Pack 2 (Build 2600) Time : Wed Sep 05 15:37:15 2007
Machine : S0022882021 Product : Microsoft SQL Server Setup Support Files (English) Product Version : 9.00.3042.00 Install : Successful Log File : c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0009_S0022882021_SQLSupport_1.log -------------------------------------------------------------------------------- Machine : S0022882021 Product : Microsoft SQL Server Native Client Product Version : 9.00.3042.00 Install : Successful Log File : c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0009_S0022882021_SQLNCLI_1.log -------------------------------------------------------------------------------- Machine : S0022882021 Product : Microsoft SQL Server VSS Writer Product Version : 9.00.3042.00 Install : Successful Log File : c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0009_S0022882021_SqlWriter_1.log -------------------------------------------------------------------------------- Machine : S0022882021 Product : MSXML 6.0 Parser Product Version : 6.10.1129.0 Install : Successful Log File : c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0009_S0022882021_MSXML6_1.log -------------------------------------------------------------------------------- Machine : S0022882021 Product : Microsoft SQL Server Setup Support Files (English) Product Version : 9.00.3042.00 Install : Successful Log File : c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0009_S0022882021_SQLSupport_2.log -------------------------------------------------------------------------------- Machine : S0022882021 Product : Microsoft SQL Server Native Client Product Version : 9.00.3042.00 Install : Successful Log File : c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0009_S0022882021_SQLNCLI_2.log -------------------------------------------------------------------------------- Machine : S0022882021 Product : MSXML 6.0 Parser Product Version : 6.10.1129.0 Install : Successful Log File : c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0009_S0022882021_MSXML6_2.log -------------------------------------------------------------------------------- Machine : S0022882021 Product : SQL Server Database Services Error : The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, "How to: View SQL Server 2005 Setup Log Files" and "Starting SQL Server Manually." -------------------------------------------------------------------------------- Machine : S0022882021 Product : Microsoft SQL Server 2005 Express Edition Product Version : 9.2.3042.00 Install : Failed Log File : c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0009_S0022882021_SQL.log Last Action : InstallFinalize Error String : Service 'SQL Server Active Directory Helper' (MSSQLServerADHelper) could not be installed. Verify that you have sufficient privileges to install system services. Error Number : 1923 -------------------------------------------------------------------------------- SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%Microsoft SQL Server90Setup BootstrapLOGSummary.txt.
I have the latest SQLEXPR and the Management Studio.
Management installed no problem.
I cannot install SQLEXPR due to beta versions of Visual Studio, etc. However this machine has been rebuilt with disk format and clean install of Windows XP Pro. No beta's of any kind on the machine.
Have latest version of Net 2, installed without error.
I installed SQLExpress with out error on other machines.
I have a problem installing SharePointRS.msi. The MSI is executing just fine, but the step "removing backups" (don't know the exact wording in english, since I'm using a german install) seems to fail.
This is what the msi logfile has to offer:
Aktion 15:59:51: RSSP_CAInstall.28B19132_4741_4761_840F_AC515130EC08. Aktion 15:59:52: RollbackCleanup. Sicherungsdateien werden entfernt CA MSG : Running RSCustomAction CA MSG : Launching C:DOKUME~1ADMINI~1LOKALE~1Temp sCustomAction.exe with command line parameter /i CA MSG : rsCustomAction.exe failed to configure, Error code is: 1 Aktion 16:02:48: Rollback. Aktion wird rückgängig gemacht:
Can anyone explain, why the custom-action is not succeeding?
Have SQL 2000 SP4 clustered instance running now. Attempted inplace upgrade to SQL 2K5 standard edition. Boxes are Windows 32 bit Ent Edition, SP2. Install wizard installed pre-req's just fine, and I got past the "components to install" box of the install wizard. When I clicked next, the current 2000 instance (already installed component) was grayed out and I could not select it. Checking the messages in the install wizard, I saw that my "upgrade was blocked". I cancelled out of the install wizard to verify all requirements.
Bounced both boxes, and now when I try to run the install wizard, it tried to install the required support files (ASP.net 2.0, SQL Native Client and what not) and then the install wizard hangs..... and never comes back. I have to kill it from taskmgr. Bounced the boxes and tried again, same thing. Install wizard hangs forever.
Yes, I am running from the active node holding the cluster resources. Yes, SQL 2000 instance is cold. Yes, I've checked add/remove programs and there is nothing to uninstall. Checked event viewer and I see the following errors:
Hanging application setup.exe, version 2005.90.1399.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000.
Fault bucket 238575085.
I've reached out to our TAM, but any help would be appreciated. No matter how many times I try, the install wizard now chokes and never comes back.
I'm running into issues installing SQL 2005 Enterprise on a Win2003 server. They seem to be related to missing rights. I've done a lot of research and have come up empty. Does anyone know why I'm getting these log entries? Thanks for any help.
Running: OpenPipeAction at: 2006/0/31 11:35:35 Complete: OpenPipeAction at: 2006/0/31 11:35:35, returned false Error: Action "OpenPipeAction" failed during execution.
Error: 0x80070005 TaskScheduler::SetTargetComputer for \SERVER Complete: RunRemoteSetupAction at: 2006/0/31 11:35:35, returned false Error: Action "RunRemoteSetupAction" failed during execution. Error information reported during run: Attempting to determine log files for remote install. Connection to remote computer's scheduler service. Error: 80070005 Access is denied.
Skipped: InstallASAction.11 Waiting for actions from remote setup(s) Breaking wait state and aborting package due to cancel code received: 1602 Remote setup(s) are ready Notify package action is determined: 1602 Error Code: 0x800700e9 (233) Windows Error Text: No process is on the other end of the pipe.
Source File Name: remotemessageliboverlappedpipelistener.cpp Compiler Timestamp: Fri Jul 29 01:13:51 2005 Function Name: sqls::OverlappedPipeListener::writePipe Source Line Number: 294 Notification failed to send.
I have a package which runs fine from the client but not the server (see error below). I am logged into the client with my domain account, and the package runs under a proxy using that same domain account (for now). The MS Access db I am trying to pull from is on a non-domain computer, and I have created a Y: mapped drive on both the client and server that access a share on that machine where the Access database lives--I created the mapped drive using the "different user" option, and used a local account on the non-domain computer to create the mapped drives.
On the server, when logged in as my domain account, I can use the y:MyDB.mdb you can see below in Start | Run to hit the Access database. Why can't the package also see this file when running on the server?
Code Snippet Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft JET Database Engine" Hresult: 0x80004005 Description: "'y:Mydb.MDB' is not a valid path. Make sure that the path name is spelled correctly and that you are connected to the server on which the file resides.". End Error Error: 2008-02-05 02:35:56.26 Code: 0xC020801C Source: Cost Cost [1] Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "MyDB" failed with error code 0xC0202009. There may be error messages posted before this with more informat... The package execution fa... The step failed.
I need some help from you on a problem with SQL Server Agent that I believe many of you have experienced. When searching on the web I find some loose answers, but it would not solve my problems. So here is my story.
1. I have created two SSIS packages, package 1 and package 2. Both packages have a Execute SQL Task making a select sql statement to a table, say Customer in AdventureWorks DB. Package1 also makes a Execute Pacakge Task to Package 2. Both packages have protectionlevel property set to EncryptSensitiveWithUserKey
2. Then I created two package configuration files per package, one indirect xml configuration and one xml configuration file. The former I created an environment variable called pack1, which was specifying the path and file name of second config file. Likewise, I did for package2. Maybe I could have reused thie first configuration file, but I am not sure since package1 calls package2.
3. Now I build and deploy my packages. Then I run my manifest file, going through the deployment wizard setting the necceccary properties like server name, user, password, I have also create the same environment variables on the deployment machine. I ensure that the package1 and package2 can be run under integration services (file system). And both package works. So far so good
4. Now I want to create a SQL server agent job that runs package1 and package2. Here I found an article that decribed How to Schedule and Run a SSIS package ( DTS ) Job in SQL Server 2005 http://www.codeproject.com/useritems/Schedule__Run__SSIS__DTS.asp
5. I created a job executor account and then Create SQL proxy account and associate proxy account with job executor account as described. I created a new ssis job, specifying type ssis integration services, run as proxy, setting package source to SSIS package store, naming the server and package name (package2).
6. Now, I try running job1 which runs package2. ANd it works. I was aware if I needed to give file permission on users (read and execute) on my dtsx/dtsconfig/log files. So far so good
7. Now, I try to run job test which runs package1 (which also runs package2). But now the job fails :-(. The job runs for some seconds, but fails. I have to say that I have some script tasks with message boxes inside!!! hope this doesn't matter. I have created all neccessary accounts, proxies, credentials and so on. here is the view history
Date 17.10.2006 00:50:53 Log Job History (test)
Step ID 1 Server ABEO-GEIR Job Name test Step Name test Duration 00:00:07 Sql Severity 0 Sql Message ID 0 Operator Emailed Operator Net sent Operator Paged Retries Attempted 0
Message Executed as user: abeo-geir as_jobuser. The package execution failed. The step failed.
Continue: This error is well known for you. It has been mentioned in many postings. Well, how do I go from here. Setting logging on the job results in only this information
PackageStart,ABEO-GEIR,ABEO-GEIR as_jobuser,Package1,{3F5BD166-D24B-4838-B3F1-018B6C2C7523},{8E1B8E45-7F1D-4C24-852C-2694F993E6D2},17.10.2006 00:59:40,17.10.2006 00:59:40,0,0x,Beginning of package execution.
PackageEnd,ABEO-GEIR,ABEO-GEIR as_jobuser,Package1,{3F5BD166-D24B-4838-B3F1-018B6C2C7523},{8E1B8E45-7F1D-4C24-852C-2694F993E6D2},17.10.2006 00:59:41,17.10.2006 00:59:41,1,0x,End of package execution.
Well, I read some place that I could run the job as type operating system (cmdexec). Here i could not choose Run as, but had to select SQL SErver agent account. NOw I got this message
Date 17.10.2006 01:05:21 Log Job History (test)
Step ID 0 Server ABEO-GEIR Job Name test Step Name (Job outcome) Duration 00:00:00 Sql Severity 0 Sql Message ID 0 Operator Emailed Operator Net sent Operator Paged Retries Attempted 0
Message The job failed. The Job was invoked by User sa. The last step to run was step 1 (test).
As you see, I can't come any further. I NEED HELP FROM YOU. I AM STUCK. I know many of you have solved this and I hope you can guide me through thise. I don't know how many hours or days I have used on this.
Had intial release installed; deleted it and associated software, and downloaded advanced, sp1 and mgmt. studio sp1.
Go to install and get just warnings(2-IIS and hardware);install goes on then fails; look at log and it says my system doesn't meet minimum hardware requirements.
Look at hardware requirements on readme and at MS and my system DOES meet 'minumum reuquirements'; he only thing close is the 512 mb minimum memory which is what my system has, 512mb memory.
1.7 P4, 30 gig of hard drive space,.net2.0,win2k with SP4,etc..
Anyone know what a workaround is or is this a 'bug'?
I am trying to install Sql Server 2005 SP2 (KB921896) on a Windows Server 2003 box that has all the other patches installed. However, the service pack fails on Databse Services and Analysis Serrvices. The Summary.txt file is listed below. I have already done some research and tried putting the NT Authority/SYSTEM in the local Administrators group but I still get the same error. Can anyone help? Thanks Time: 06/21/2007 15:30:09.610 KB Number: KB921896 Machine: PDSQL OS Version: Microsoft Windows Server 2003 family, Standard Edition Service Pack 2 (Build 3790) Package Language: 1033 (ENU) Package Platform: x86 Package SP Level: 2 Package Version: 3042 Command-line parameters specified: Cluster Installation: No
********************************************************************************** Prerequisites Check & Status SQLSupport: Passed
********************************************************************************** Products Detected Language Level Patch Level Platform Edition Setup Support Files ENU 9.2.3042 x86 Database Services (MSSQLSERVER) ENU SP1 2005.090.2047.00 x86 STANDARD Analysis Services (MSSQLSERVER) ENU SP1 2005.090.2047.00 x86 STANDARD Reporting Services (MSSQLSERVER) ENU SP2 9.00.3054.00 x86 STANDARD Notification Services ENU SP2 9.00.3054.00 x86 STANDARD Integration Services ENU SP2 9.00.3054.00 x86 STANDARD SQL Server Native Client ENU 9.00.3042.00 x86 Client Components ENU SP2 9.2.3054 x86 STANDARD MSXML 6.0 Parser ENU 6.10.1129.0 x86 SQLXML4 ENU 9.00.3042.00 x86 Backward Compatibility ENU 8.05.2004 x86 Microsoft SQL Server VSS Writer ENU 9.00.3042.00 x86
********************************************************************************** Products Disqualified & Reason Product Reason Reporting Services (MSSQLSERVER) The product instance MSSQLSERVER been patched with more recent updates. Notification Services The product instance NS been patched with more recent updates. Integration Services The product instance Integration Services been patched with more recent updates. Client Components The product instance SQL Tools been patched with more recent updates.
********************************************************************************** Processes Locking Files Process Name Feature Type User Name PID msftesql Database Services Service NT AUTHORITYSYSTEM 3464 SQLBrowser Database Services Service NT AUTHORITYSYSTEM 5276
********************************************************************************** Product Installation Status Product : Setup Support Files Product Version (Previous): 3042 Product Version (Final) : Status : Not Selected Log File : Error Description : ---------------------------------------------------------------------------------- Product : Database Services (MSSQLSERVER) Product Version (Previous): 2047 Product Version (Final) : Status : Failure Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQL9_Hotfix_KB921896_sqlrun_sql.msp.log Error Number : 29512 Error Description : MSP Error: 29512 SQL Server Setup was unable add user NT AUTHORITYSYSTEM to local group PERSONNELALSQLServer2005SQLAgentUser$PDSQL$MSSQLSERVER. ---------------------------------------------------------------------------------- Product : Analysis Services (MSSQLSERVER) Product Version (Previous): 2047 Product Version (Final) : Status : Failure Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixOLAP9_Hotfix_KB921896_sqlrun_as.msp.log Error Number : 29512 Error Description : MSP Error: 29512 SQL Server Setup was unable add user NT AUTHORITYSYSTEM to local group PERSONNELALSQLServer2005MSOLAPUser$PDSQL$MSSQLSERVER. ---------------------------------------------------------------------------------- Product : Reporting Services (MSSQLSERVER) Product Version (Previous): 3054 Product Version (Final) : Status : NA Log File : Error Description : The product instance MSSQLSERVER been patched with more recent updates. ---------------------------------------------------------------------------------- Product : Notification Services Product Version (Previous): 3054 Product Version (Final) : Status : NA Log File : Error Description : The product instance NS been patched with more recent updates. ---------------------------------------------------------------------------------- Product : Integration Services Product Version (Previous): 3054 Product Version (Final) : Status : NA Log File : Error Description : The product instance Integration Services been patched with more recent updates. ---------------------------------------------------------------------------------- Product : SQL Server Native Client Product Version (Previous): 3042 Product Version (Final) : Status : Not Selected Log File : Error Description : ---------------------------------------------------------------------------------- Product : Client Components Product Version (Previous): 3054 Product Version (Final) : Status : NA Log File : Error Description : The product instance SQL Tools been patched with more recent updates. ---------------------------------------------------------------------------------- Product : MSXML 6.0 Parser Product Version (Previous): 1129 Product Version (Final) : Status : Not Selected Log File : Error Description : ---------------------------------------------------------------------------------- Product : SQLXML4 Product Version (Previous): 3042 Product Version (Final) : Status : Not Selected Log File : Error Description : ---------------------------------------------------------------------------------- Product : Backward Compatibility Product Version (Previous): 2004 Product Version (Final) : Status : Not Selected Log File : Error Description : ---------------------------------------------------------------------------------- Product : Microsoft SQL Server VSS Writer Product Version (Previous): 3042 Product Version (Final) : Status : Not Selected Log File : Error Description : ----------------------------------------------------------------------------------
********************************************************************************** Summary One or more products failed to install, see above for details Exit Code Returned: 29512
I'm having a problem installing SQL Server 2005 and I hope someone can give me an idea how to proceed. I have two machines and it works fine on one but fails to install on the other. The maddening thing is that the message reporting the failure gives me absolutely no feedback other than that the install failed.
I downloaded VB 2005 Express with MSDN and SQL Server 2005 Express. The .NET framework, VB and MSDN installed fine and then it failed on SQL Server. I have uninstalled and tried again several times with the same results. There's nothing unusual about my PC. It's relatively new with plenty of memory and disk storage. It's a Dell PC with a 2.4GHZ processor. There is another database product running on this system. Is that likely to be an issue?
I can't seem to install SQL Server 2005 (x64 version) on an x64 Win2k3 two node cluster.
I get all the way through the configuration and setup fails because it cannot start a task on the remote node. The error message indicates to check the task scheduler log file, which I have and I cannot find any 'errors' in the file.
Google/MSDN/Technet turn up nothing on multiple searches. Has anyone else run into this problem?
My installation account is a local admin on both machines, so is the sql cluster account. For the life of me I cannot figure out what's different for an x64 install vs 32bit....
I'm not sure if this is correct but this installs all the components properly except "Microsoft SQL Server 2005". This component failes with the below error. ---------------------------------------------------------------------------------------------------- Event Type: Error Event Source: MsiInstaller Event Category: None Event ID: 10005 Date: 4/8/2008 Time: 3:33:03 PM User: NT AUTHORITYSYSTEM Computer: HYDTEST15 Description: Product: Microsoft SQL Server 2005 -- Error 29503. The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, "How to: View SQL Server 2005 Setup Log Files" and "Starting SQL Server Manually." The error is (1067) The process terminated unexpectedly. ----------------------------------------------------------------------------------------------------
Actually I didn''t know how to install SQL to run the services with Syatem account. I read through some forums and found that I should use domain account for this purpose. If I dont give any account details Installation will fail saying the account details for service are not specified.
I thought of running the installation with any domain account and then use a script to chage the sevice to run with system account so that user can use it.
I have the log file but its a 12 mb file. I couldn't find an option to install attach the file.
I'm experiencing a problem installing SQL Server Express 2005. I thought I had the same problem as Tom from a recent thread but his error file is quite different from mine. The Visual Basic Express package properly installed everything except SQL Server. I've run it many times, but the service fails to start. I also downloaded the separate installation package for SQL Server Express and ran it several times, which also failed. It gets to a point where the services are installed, but when I try to manually start the SQL service it says that the service started and then stopped. The event viewer shows this error:
Product: Microsoft SQL Server 2005 Express Edition -- Error 29503. The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, "How to: View SQL Server 2005 Setup Log Files" and "Starting SQL Server Manually." The error is (1067) The process terminated unexpectedly.
The error log is:
2006-05-02 16:10:58.07 Server Microsoft SQL Server 2005 - 9.00.2047.00 (Intel X86) Apr 14 2006 01:12:25 Copyright (c) 1988-2005 Microsoft Corporation Express Edition on Windows NT 5.1 (Build 2600: Service Pack 2)
2006-05-02 16:10:58.08 Server (c) 2005 Microsoft Corporation. 2006-05-02 16:10:58.08 Server All rights reserved. 2006-05-02 16:10:58.09 Server Server process ID is 816. 2006-05-02 16:10:58.09 Server Logging SQL Server messages in file 'c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLLOGERRORLOG'. 2006-05-02 16:10:58.09 Server This instance of SQL Server last reported using a process ID of 2748 at 5/2/2006 4:10:29 PM (local) 5/2/2006 9:10:29 PM (UTC). This is an informational message only; no user action is required. 2006-05-02 16:10:58.15 Server Registry startup parameters: 2006-05-02 16:10:58.15 Server -d c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLDATAmaster.mdf 2006-05-02 16:10:58.15 Server -e c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLLOGERRORLOG 2006-05-02 16:10:58.16 Server -l c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLDATAmastlog.ldf 2006-05-02 16:10:58.28 Server Error: 17311, Severity: 16, State: 1. 2006-05-02 16:10:58.28 Server SQL Server is terminating because of fatal exception c000001d. This error may be caused by an unhandled Win32 or C++ exception, or by an access violation encountered during exception handling. Check the SQL error log for any related stack dumps or messages. This exception forces SQL Server to shutdown. To recover from this error, restart the server (unless SQLAgent is configured to auto restart). 2006-05-02 16:10:58.30 Server Using 'dbghelp.dll' version '4.0.5' 2006-05-02 16:10:58.36 Server **Dump thread - spid = 0, PSS = 0x00000000, EC = 0x00000000 2006-05-02 16:10:58.36 Server ***Stack Dump being sent to c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLLOGSQLDump0005.txt 2006-05-02 16:10:58.36 Server * ******************************************************************************* 2006-05-02 16:10:58.36 Server * 2006-05-02 16:10:58.36 Server * BEGIN STACK DUMP: 2006-05-02 16:10:58.36 Server * 05/02/06 16:10:58 spid 0 2006-05-02 16:10:58.36 Server * 2006-05-02 16:10:58.36 Server * ex_handle_except encountered exception C000001D - Server terminating 2006-05-02 16:10:58.36 Server * 2006-05-02 16:10:58.36 Server * 2006-05-02 16:10:58.36 Server * MODULE BASE END SIZE 2006-05-02 16:10:58.36 Server * sqlservr 01000000 02BCEFFF 01bcf000 2006-05-02 16:10:58.36 Server * ntdll 7C900000 7C9AFFFF 000b0000 2006-05-02 16:10:58.36 Server * kernel32 7C800000 7C8F3FFF 000f4000 2006-05-02 16:10:58.36 Server * MSVCR80 78130000 781CAFFF 0009b000 2006-05-02 16:10:58.36 Server * msvcrt 77C10000 77C67FFF 00058000 2006-05-02 16:10:58.37 Server * MSVCP80 7C420000 7C4A6FFF 00087000 2006-05-02 16:10:58.37 Server * ADVAPI32 77DD0000 77E6AFFF 0009b000 2006-05-02 16:10:58.37 Server * RPCRT4 77E70000 77F00FFF 00091000 2006-05-02 16:10:58.37 Server * USER32 77D40000 77DCFFFF 00090000 2006-05-02 16:10:58.37 Server * GDI32 77F10000 77F56FFF 00047000 2006-05-02 16:10:58.37 Server * CRYPT32 77A80000 77B13FFF 00094000 2006-05-02 16:10:58.37 Server * MSASN1 77B20000 77B31FFF 00012000 2006-05-02 16:10:58.37 Server * Secur32 77FE0000 77FF0FFF 00011000 2006-05-02 16:10:58.37 Server * MSWSOCK 71A50000 71A8EFFF 0003f000 2006-05-02 16:10:58.37 Server * WS2_32 71AB0000 71AC6FFF 00017000 2006-05-02 16:10:58.37 Server * WS2HELP 71AA0000 71AA7FFF 00008000 2006-05-02 16:10:58.37 Server * USERENV 769C0000 76A72FFF 000b3000 2006-05-02 16:10:58.37 Server * opends60 333E0000 333E6FFF 00007000 2006-05-02 16:10:58.37 Server * NETAPI32 5B860000 5B8B3FFF 00054000 2006-05-02 16:10:58.37 Server * SHELL32 7C9C0000 7D1D4FFF 00815000 2006-05-02 16:10:58.37 Server * SHLWAPI 77F60000 77FD5FFF 00076000 2006-05-02 16:10:58.37 Server * OCMAPIHK 10000000 1000CFFF 0000d000 2006-05-02 16:10:58.37 Server * comctl32 773D0000 774D1FFF 00102000 2006-05-02 16:10:58.37 Server * comctl32 5D090000 5D126FFF 00097000 2006-05-02 16:10:58.37 Server * psapi 76BF0000 76BFAFFF 0000b000 2006-05-02 16:10:58.37 Server * instapi 48060000 48069FFF 0000a000 2006-05-02 16:10:58.37 Server * sqlevn70 4F610000 4F7A3FFF 00194000 2006-05-02 16:10:58.37 Server * dbghelp 03000000 03112FFF 00113000 2006-05-02 16:10:58.37 Server * 2006-05-02 16:10:58.37 Server * Edi: 0075C528: 000E1068 00000000 00000000 00000000 0075C548 00000000 2006-05-02 16:10:58.37 Server * Esi: 00000000: 2006-05-02 16:10:58.37 Server * Eax: 0075C40C: 000042AC 00000000 00000000 7C81EB33 00000000 0000000C 2006-05-02 16:10:58.37 Server * Ebx: 0000003F: 2006-05-02 16:10:58.38 Server * Ecx: 0075CA7C: 00000000 0001001F 00000000 00000000 00000000 00000000 2006-05-02 16:10:58.38 Server * Edx: 0000003D: 2006-05-02 16:10:58.38 Server * Eip: 7C81EB33: 10C2C95E 0FFF8500 FED0E68E FC558BFF 0F0C5589 7D8B16B7 2006-05-02 16:10:58.38 Server * Ebp: 0075C45C: 0075C4A0 02187744 000042AC 00000000 00000000 00000000 2006-05-02 16:10:58.38 Server * SegCs: 0000001B: 2006-05-02 16:10:58.38 Server * EFlags: 00080246: 2006-05-02 16:10:58.38 Server * Esp: 0075C408: 00000000 000042AC 00000000 00000000 7C81EB33 00000000 2006-05-02 16:10:58.38 Server * SegSs: 00000023: 2006-05-02 16:10:58.38 Server * ******************************************************************************* 2006-05-02 16:10:58.38 Server * ------------------------------------------------------------------------------- 2006-05-02 16:10:58.38 Server * Short Stack Dump 2006-05-02 16:10:58.50 Server 7C81EB33 Module(kernel32+0001EB33) 2006-05-02 16:10:58.50 Server 02187744 Module(sqlservr+01187744) 2006-05-02 16:10:58.51 Server 0218B600 Module(sqlservr+0118B600) 2006-05-02 16:10:58.51 Server 0218B1AD Module(sqlservr+0118B1AD) 2006-05-02 16:10:58.51 Server 023F4109 Module(sqlservr+013F4109) 2006-05-02 16:10:58.51 Server 7C862CD3 Module(kernel32+00062CD3) 2006-05-02 16:10:58.57 Server 7C83AA6B Module(kernel32+0003AA6B) 2006-05-02 16:10:58.60 Server Stack Signature for the dump is 0xDF483EDE 2006-05-02 16:10:59.33 Server External dump process return code 0x20000001. External dump process returned no errors.
