SQL Server 2005 SP2 install on Vista

Hi,
I have all updates for Vista, tried to install SQL Server 2005 SP2, the following log file:
Microsoft SQL Server 2005 9.00.3042.00
==============================
OS Version      : Professional  (Build 6000)
Time            : Wed Mar 26 12:20:54 2008
USER-PC : To change an existing instance of Microsoft SQL Server 2005 to a different edition of SQL Server 2005, you must run SQL Server 2005 Setup from the command prompt and include the SKUUPGRADE=1 parameter.
Machine         : USER-PC
Product         : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.3042.00
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_USER-PC_SQLSupport_1.log
Machine         : USER-PC
Product         : Microsoft SQL Server Native Client
Product Version : 9.00.3042.00
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_USER-PC_SQLNCLI_1.log
Machine         : USER-PC
Product         : Microsoft SQL Server VSS Writer
Product Version : 9.00.3042.00
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_USER-PC_SqlWriter_1.log
Machine         : USER-PC
Product         : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.3042.00
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_USER-PC_SQLSupport_2.log
Machine         : USER-PC
Product         : Microsoft SQL Server Native Client
Product Version : 9.00.3042.00
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_USER-PC_SQLNCLI_2.log
Machine         : USER-PC
Product         : Microsoft SQL Server 2005 Express Edition
Product Version : 9.00.1399.06
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_USER-PC_SQL.log
Machine         : USER-PC
Product         : Workstation Components, Books Online and Development Tools
Warning         : Warning 28123.Warning: SQL Server Setup cannot install this feature because a different edition of this feature is already installed. For more information, see 'Version and Edition Upgrades' in SQL Server Books Online.
Machine         : USER-PC
Product         : Microsoft SQL Server 2005 Tools Express Edition
Product Version : 9.00.1399.06
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_USER-PC_Tools.log
 Setup succeeded with the installation, inspect the log file completely for status on all the components.
Time            : Wed Mar 26 12:23:51 2008
==============================================================
When I try to start SQL Server it times out. SQL Server Express is running ok.
Can you help me get this started?
Thank you,
Lucy

This is the previous errorlog:
2008-04-09 11:47:06.27 Server      Microsoft SQL Server 2005 - 9.00.3054.00 (Intel X86)
 Mar 23 2007 16:28:52
 Copyright (c) 1988-2005 Microsoft Corporation
 Enterprise Evaluation Edition on Windows NT 6.0 (Build 6000: )
2008-04-09 11:47:06.27 Server      (c) 2005 Microsoft Corporation.
2008-04-09 11:47:06.27 Server      All rights reserved.
2008-04-09 11:47:06.27 Server      Server process ID is 240.
2008-04-09 11:47:06.27 Server      Authentication mode is WINDOWS-ONLY.
2008-04-09 11:47:06.27 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2008-04-09 11:47:06.27 Server      This instance of SQL Server last reported using a process ID of 4180 at 4/5/2008 11:17:36 AM (local) 4/5/2008 6:17:36 PM (UTC). This is an informational message only; no user action is required.
2008-04-09 11:47:06.27 Server      Registry startup parameters:
2008-04-09 11:47:06.27 Server        -d C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2008-04-09 11:47:06.27 Server        -e C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2008-04-09 11:47:06.27 Server        -l C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2008-04-09 11:47:06.32 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2008-04-09 11:47:06.32 Server      Detected 2 CPUs. This is an informational message; no user action is required.
2008-04-09 11:47:06.50 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.
2008-04-09 11:47:06.55 Server      Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
2008-04-09 11:47:06.64 Server      The Microsoft Distributed Transaction Coordinator (MS DTC) service could not be contacted.  If you would like distributed transaction functionality, please start this service.
2008-04-09 11:47:06.64 Server      Database mirroring has been enabled on this instance of SQL Server.
2008-04-09 11:47:06.64 spid4s      Starting up database 'master'.
2008-04-09 11:47:06.80 spid4s      4 transactions rolled forward in database 'master' (1). This is an informational message only. No user action is required.
2008-04-09 11:47:06.82 spid4s      0 transactions rolled back in database 'master' (1). This is an informational message only. No user action is required.
2008-04-09 11:47:06.82 spid4s      Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2008-04-09 11:47:07.06 spid4s      SQL Trace ID 1 was started by login "sa".
2008-04-09 11:47:07.10 spid4s      Starting up database 'mssqlsystemresource'.
2008-04-09 11:47:07.13 spid4s      The resource database build version is 9.00.3042. This is an informational message only. No user action is required.
2008-04-09 11:47:07.34 spid4s      Server name is 'USER-PC'. This is an informational message only. No user action is required.
2008-04-09 11:47:07.34 spid9s      Starting up database 'model'.
2008-04-09 11:47:07.53 spid9s      Clearing tempdb database.
2008-04-09 11:47:08.11 Server      A self-generated certificate was successfully loaded for encryption.
2008-04-09 11:47:08.11 Server      Server is listening on [ 'any' <ipv6> 1433].
2008-04-09 11:47:08.11 Server      Server is listening on [ 'any' <ipv4> 1433].
2008-04-09 11:47:08.17 Server      Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2008-04-09 11:47:08.17 Server      Server named pipe provider is ready to accept connection on [ \\.\pipe\sql\query ].
2008-04-09 11:47:08.17 Server      Server is listening on [ ::1 <ipv6> 1434].
2008-04-09 11:47:09.12 spid9s      Starting up database 'tempdb'.
2008-04-09 11:47:09.47 spid12s     The Service Broker protocol transport is disabled or not configured.
2008-04-09 11:47:09.47 spid12s     The Database Mirroring protocol transport is disabled or not configured.
2008-04-09 11:47:09.53 spid12s     Service Broker manager has started.
2008-04-09 11:51:06.92 Server      CPU time stamp frequency has changed from 1662000 to 199683 ticks per millisecond. The new frequency will be used.
2008-04-09 11:55:07.29 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2008-04-09 11:55:07.29 Server      CPU time stamp frequency has changed from 199683 to 136029 ticks per millisecond. The new frequency will be used.
2008-04-09 12:23:09.84 Server      CPU time stamp frequency has changed from 136029 to 586928 ticks per millisecond. The new frequency will be used.
2008-04-09 12:59:13.12 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2008-04-09 13:07:13.85 Server      CPU time stamp frequency has changed from 586928 to 824822 ticks per millisecond. The new frequency will be used.
2008-04-09 13:47:17.50 Server      CPU time stamp frequency has changed from 824822 to 140502 ticks per millisecond. The new frequency will be used.
2008-04-09 14:07:19.33 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2008-04-09 15:07:24.80 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2008-04-09 15:11:25.16 Server      CPU time stamp frequency has changed from 140502 to 1413355 ticks per millisecond. The new frequency will be used.
2008-04-09 15:15:25.53 Server      CPU time stamp frequency has changed from 1413355 to 161989 ticks per millisecond. The new frequency will be used.
2008-04-09 15:19:25.89 Server      CPU time stamp frequency has changed from 161989 to 134822 ticks per millisecond. The new frequency will be used.
2008-04-09 16:23:31.73 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2008-04-09 17:23:37.20 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2008-04-09 18:11:41.58 Server      CPU time stamp frequency has changed from 134822 to 154257 ticks per millisecond. The new frequency will be used.
2008-04-09 18:23:42.67 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2008-04-09 18:23:42.67 Server      CPU time stamp frequency has changed from 154257 to 134721 ticks per millisecond. The new frequency will be used.
2008-04-09 18:35:43.79 Server      CPU time stamp frequency has changed from 134721 to 151448 ticks per millisecond. The new frequency will be used.
2008-04-09 18:43:44.51 Server      CPU time stamp frequency has changed from 151448 to 125134 ticks per millisecond. The new frequency will be used.
2008-04-09 19:15:47.35 Server      CPU time stamp frequency has changed from 125134 to 182297 ticks per millisecond. The new frequency will be used.
2008-04-09 19:23:48.08 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2008-04-09 19:27:48.45 Server      CPU time stamp frequency has changed from 182297 to 120770 ticks per millisecond. The new frequency will be used.
2008-04-09 19:47:50.27 Server      CPU time stamp frequency has changed from 120770 to 1370171 ticks per millisecond. The new frequency will be used.
2008-04-09 20:07:52.10 Server      CPU time stamp frequency has changed from 1370171 to 106932 ticks per millisecond. The new frequency will be used.
2008-04-09 20:23:53.56 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2008-04-09 20:35:54.65 Server      CPU time stamp frequency has changed from 106932 to 88924 ticks per millisecond. The new frequency will be used.
2008-04-09 20:51:56.11 Server      CPU time stamp frequency has changed from 88924 to 102106 ticks per millisecond. The new frequency will be used.
2008-04-09 20:59:56.84 Server      CPU time stamp frequency has changed from 102106 to 118592 ticks per millisecond. The new frequency will be used.

Similar Messages

  • What Drivers should I use to access SQL Server 2005 SP2 from Windows Server 2008 64 bit

    and yes I do know that is an odd scenario so let me explain
    I have just joined a project that is "in flight" where the customer is upgrading a LOT of things at the same time
    (some Microsoft, some other supplier: some at the OS level, others at server or services levels)
    the current step is replacing some services leaving the back end databases as they are
    i.e. SQL Server 2005 SP2
    a later step will upgrade the backend data bases which may make more work
    What we have now runs on Windows Server 2003 32 bit using the OLEDB drivers
    version 2000.86.3959.00
    What we want must run on Windows Server 2008 64 bit still using the OLEDB option
    which version should I download & try to install?

    Here are a known list of issues with this configuration with their corresponding workarounds: https://support.microsoft.com/kb/936302/en-us
    Satish Kartan www.sqlfood.com

  • Package developed on SQL Server 2005 SP1 not opening in SQL Server 2005 SP2

    Recently I have upgraded my system to SQL Server 2005 SP2 version 9.00.3054; I have developed my packages on SQL Server 2005 SP1 version 9.00.2047. I am unable to open all these packages on SQL Serever SP2 version 9.00.3054 it is giving me error.
    Error: Error loading Package.dtsx cannot create an instance of the XML Document Object Model. MSXML may not be registered. 
    Can any body help me in this?
    Thanks in advance

    Try the search function.
    http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1446338&SiteID=1

  • SQL Server 2005 SP2 Failed to install the update

    I just purchased a Dell PC and during the start up one of the updates that tried to install was SQL Server 2005. I tried turning off my Anti Virus program and the install failed again. Everything I've read about this problem is too technical for me. Is
    there a simple way to fix this problem?

    I just purchased a Dell PC and during the start up one of the updates that tried to install was SQL Server 2005. I tried turning off my Anti Virus program and the install failed again. Everything I've read about this problem is too technical for
    me. Is there a simple way to fix this problem?
    I am curious which Windows update installs SQL server 2005. Were you installing any program which installed SQL 2005 as part of it ?
    Anyways you can share log file as asked by Alberto. Please also give more details whether SQL server was installed by you or machine or whether it was SQL 2005 update.
    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

  • XP_DELETE_FILE NOT WORKING IN SQL SERVER 2005 SP2

    Hi All,
    I have one job in sql 2005 sp2 that deletes backup older than one week.It is not working.I have checked service account permissions on backup folder and all required permissions and authentications are in place.Please let me know how to troubleshoot the
    same.
    Regards
    Rahul 

    Check the following:
    http://stackoverflow.com/questions/212603/sql-server-xp-delete-file-not-deleting-files
    QUOTE: "Note that xp_delete_file is broken in SP2 and won't work on report files;"
    Kalman Toth Database & OLAP Architect
    SQL Server 2014 Design & Programming
    New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012

  • SQL Server 2012 SP2 Install error

    The SQL Server SP2 update fails as follows on my ALwaysOn Secondary node

    Thanks for this information
    Check in C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap. There is
    a log directory for each install attempt. It should give you more information
    on what happened.<o:p></o:p>
    It gave me something to look at. I first checked the Summary file for that install time and then looked at the Detail txt file but I can't understand what is causing the problem. Here are the final lines in that file. Any ideas?
    Completed Action: RunPatchAllInstanceAction, returned True
    (01) 2015-02-05 15:53:01 Slp: ----------------------------------------------------------------------
    (01) 2015-02-05 15:53:01 Slp: Skipping Action: ValidatePatchInstanceName due to user cancel request
    (01) 2015-02-05 15:53:01 Slp: ----------------------------------------------------------------------
    (01) 2015-02-05 15:53:01 Slp: Skipping Action: ExecutePatchCalculateWorkflow due to user cancel request
    (01) 2015-02-05 15:53:01 Slp: ----------------------------------------------------------------------
    (01) 2015-02-05 15:53:01 Slp: Skipping Action: FinalCalculateSettings due to user cancel request
    (01) 2015-02-05 15:53:01 Slp: ----------------------------------------------------------------------
    (01) 2015-02-05 15:53:01 Slp: Skipping Action: ValidateFeatureSettings due to user cancel request
    (01) 2015-02-05 15:53:01 Slp: ----------------------------------------------------------------------
    (01) 2015-02-05 15:53:01 Slp: Skipping Action: SchedulePackageInstallActionsAction due to user cancel request
    (01) 2015-02-05 15:53:01 Slp: ----------------------------------------------------------------------
    (01) 2015-02-05 15:53:01 Slp: Skipping Action: ScheduleUpgradePackageInstallActionsAction due to user cancel request
    (01) 2015-02-05 15:53:01 Slp: ----------------------------------------------------------------------
    (01) 2015-02-05 15:53:01 Slp: Skipping Action: ScheduleConfigAction due to user cancel request
    (01) 2015-02-05 15:53:01 Slp: ----------------------------------------------------------------------
    (01) 2015-02-05 15:53:01 Slp: Skipping Action: NotifyProgressCountDisplay due to user cancel request
    (01) 2015-02-05 15:53:01 Slp: ----------------------------------------------------------------------
    (01) 2015-02-05 15:53:01 Slp: Skipping Action: ValidationTimingConfigAction due to user cancel request
    (01) 2015-02-05 15:53:01 Slp: ----------------------------------------------------------------------
    (01) 2015-02-05 15:53:01 Slp: Skipping Action: PreMsiTimingConfigAction due to user cancel request
    (01) 2015-02-05 15:53:01 Slp: ----------------------------------------------------------------------
    (01) 2015-02-05 15:53:01 Slp: Skipping Action: StopPatchedServices due to user cancel request
    (01) 2015-02-05 15:53:01 Slp: ----------------------------------------------------------------------
    (01) 2015-02-05 15:53:01 Slp: Skipping Action: CachePatchPage due to user cancel request
    (01) 2015-02-05 15:53:01 Slp: ----------------------------------------------------------------------
    (01) 2015-02-05 15:53:01 Slp: Skipping Action: InitializeMsiAction due to user cancel request
    (01) 2015-02-05 15:53:01 Slp: ----------------------------------------------------------------------
    (01) 2015-02-05 15:53:01 Slp: Skipping Action: MsiTimingAction due to user cancel request
    (01) 2015-02-05 15:53:01 Slp: ----------------------------------------------------------------------
    (01) 2015-02-05 15:53:01 Slp: Skipping Action: FinalizeMsiAction due to user cancel request
    (01) 2015-02-05 15:53:01 Slp: ----------------------------------------------------------------------
    (01) 2015-02-05 15:53:01 Slp: Skipping Action: PostMsiTimingConfigAction due to user cancel request
    (01) 2015-02-05 15:53:01 Slp: ----------------------------------------------------------------------
    (01) 2015-02-05 15:53:01 Slp: Skipping Action: DowntimeTimingConfigAction due to user cancel request
    (01) 2015-02-05 15:53:01 Slp: ----------------------------------------------------------------------
    (01) 2015-02-05 15:53:01 Slp: Skipping Action: StartPatchedServices due to user cancel request
    (01) 2015-02-05 15:53:01 Slp: ----------------------------------------------------------------------
    (01) 2015-02-05 15:53:01 Slp: Skipping Action: StartupTimingConfigAction due to user cancel request
    (01) 2015-02-05 15:53:01 Slp: ----------------------------------------------------------------------
    (01) 2015-02-05 15:53:01 Slp: Skipping Action: PreUninstallTimingConfigAction due to user cancel request
    (01) 2015-02-05 15:53:01 Slp: ----------------------------------------------------------------------
    (01) 2015-02-05 15:53:01 Slp: Skipping Action: UninstallTimingConfigAction due to user cancel request
    (01) 2015-02-05 15:53:01 Slp: ----------------------------------------------------------------------
    (01) 2015-02-05 15:53:01 Slp: Skipping Action: UpgradeMsiTimingAction due to user cancel request
    (01) 2015-02-05 15:53:01 Slp: ----------------------------------------------------------------------
    (01) 2015-02-05 15:53:01 Slp: Skipping Action: FinalizeTimingConfigAction due to user cancel request
    (01) 2015-02-05 15:53:01 Slp: ----------------------------------------------------------------------
    (01) 2015-02-05 15:53:01 Slp: Skipping Action: CreateARPRegKeyAction due to user cancel request
    (01) 2015-02-05 15:53:01 Slp: ----------------------------------------------------------------------
    (01) 2015-02-05 15:53:01 Slp: Skipping Action: NotifyProgressComplete due to user cancel request
    (01) 2015-02-05 15:53:01 Slp: ----------------------------------------------------------------------
    (01) 2015-02-05 15:53:01 Slp: Skipping Action: DetermineProductFeatureSummary
    (01) 2015-02-05 15:53:01 Slp: Action is being skipped due to the following restrictions:
    (01) 2015-02-05 15:53:01 Slp: Condition "Is the datastore flag /Scenario/Patching/IsRunningInnerSetup set" did not pass as it returned false and true was expected.
    (01) 2015-02-05 15:53:01 Slp: ----------------------------------------------------------------------
    (01) 2015-02-05 15:53:01 Slp: Running Action: FinalizeProgressStatus
    (01) 2015-02-05 15:53:01 Slp: Completed Action: FinalizeProgressStatus, returned True
    (01) 2015-02-05 15:53:01 Slp: ----------------------------------------------------------------------
    (01) 2015-02-05 15:53:01 Slp: Running Action: CloseUI
    (01) 2015-02-05 15:53:01 Slp: Stop action skipped in UI Mode Quiet
    (01) 2015-02-05 15:53:01 Slp: Completed Action: CloseUI, returned True
    (01) 2015-02-05 15:53:01 Slp: Sco: File 'C:\Windows\system32\Cluster.exe' does not exist
    (01) 2015-02-05 15:53:01 Slp: Failed to collect cluster logs, cannot find Cluster.exe under system directory.
    (01) 2015-02-05 15:53:01 Slp: Dumping final cluster state.
    (01) 2015-02-05 15:53:03 Slp: Completed dumping final cluster state.
    (01) 2015-02-05 15:53:05 Slp:
    (01) 2015-02-05 15:53:05 Slp:
    (01) 2015-02-05 15:53:05 Slp: ----------------------------------------------------------------------
    (01) 2015-02-05 15:53:05 Slp:
    (01) 2015-02-05 15:53:05 Slp: Error result: -2061893564
    (01) 2015-02-05 15:53:05 Slp: Result facility code: 1306
    (01) 2015-02-05 15:53:05 Slp: Result error code: 68
    (01) 2015-02-05 15:53:05 Slp: SQM Service: Sqm does not have active session.

  • Troble configuring Hyperion Shared Services with SQL Server 2005

    I recently installed SQL server (SQL SERVER 2005) in my machine and then am trying to install Hyperion (9.3.1) products. I started with Shared services. It was installed successfully. Problem is occuring when am trying to configure Shared service with SQL database using Hyperion Configuration utility (9.3.1)
    The error which is popping up is
    Unable to connect to the database for the product Hyperion Shared Services.
    Things which I tried from my end
    1. Made sure TCP IP Protocol was enabled in SQL server configuration server.
    2. hypuser was created in SQl server.
    3. hypdb was created in SQL server.
    4. Was having dynamic IP address so install Loopback adapter to obtain Static IP address and port.
    5. Port and IP address was correct.
    Let me know where I am going wrong.
    Any help will be greatly appreciated.

    Finally got it fixed firewall settings needed to be change : This document helped me a lot to troubleshoot the issue
    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. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 2)
    This problem may occur when SQL Server 2005 is not configured to accept incoming local and remote connections, which is disabled by default in SQL Server 2005 Express Edition, SQL Server 2005 Developer Edition and also SQL Server 2005 Enterprise Edition. To solve the connection forbidden problem, SQL Server 2005 needs to configure to allow incoming local and remote connections.
    Firstly, ensure that SQL Server 2005 is configured properly to allow incoming connections on the instance of database server, else enable and turn on the local and remote connections setting.
    Click Start button, then go to Programs or All Programs, then select Microsoft SQL Server 2005, followed by Configuration Tools. Click and run the SQL Server Surface Area Configuration.
    On the “SQL Server 2005 Surface Area Configuration” page, click Surface Area Configuration for Services and Connections.
    On the “Surface Area Configuration for Services and Connections” page, expand Database Engine tree, click Remote Connections.
    Select Local and remote connections, or Local connections only which applicable only if there is no remote system tries to connect to the SQL Server, useful when you just trying to connect and authenticate with the server after installing.
    Select the appropriate protocol to enable to local and/or remote connections environment. To ensure maximum compatibility, select Using both TCP/IP and named pipes.
    Click Apply button when done.
    Click OK button when prompted with the message saying that “Changes to Connection Settings will not take effect until you restart the Database Engine service.”
    On the “Surface Area Configuration for Services and Connections” page, expand Database Engine, then click Service.
    Click Stop button to stop the SQL Server service.
    Wait until the MSSQLSERVER service stops, and then click Start button to restart the MSSQLSERVER service.
    Secondly, SQL Server Browser service has to be enabled to allow for local and remote connections if SQL Server 2005 is running by using an instance name and users are not using a specific TCP/IP port number in the connection string.
    Click Start button, then go to Programs or All Programs, then select Microsoft SQL Server 2005, followed by Configuration Tools. Click and run the SQL Server Surface Area Configuration.
    On the “SQL Server 2005 Surface Area Configuration” page, click Surface Area Configuration for Services and Connections.
    On the “Surface Area Configuration for Services and Connections” page, click SQL Server Browser.
    Select Automatic as the Startup type to start SQL Server Browser service automatically every time system starts.
    Click Apply button.
    Click on Start button to start the service immediately.
    Click OK button.
    Finally, if remote computer needs to connect and access SQL Server, an exceptions in Windows Firewall included in Windows XP SP2 (Service Pack 2), Windows Server 2003 and Windows Vista needs to be created. If you’re using third-party firewall system, the exception rules also needed to be created to allow external remote connections to the SQL Server 2005 and SQL Server Browser Service to communicate through the firewall, else connections will be blocked. Consult the firewall manual for more details. Each instance of SQL Server 2005 must have its own exception, together with an exclusion for SQL Server Browser service.
    SQL Server 2005 uses an instance ID as part of the path when you install its program files. To create an exception for each instance of SQL Server, you must identify the correct instance ID. To obtain an instance ID, follow these steps:
    Click Start button, then go to Programs or All Programs, then select Microsoft SQL Server 2005, followed by Configuration Tools. Click and run the SQL Server Configuration Manager.
    In “SQL Server Configuration Manager”, click the SQL Server Browser service in the right pane, right-click the instance name in the main window, and then click Properties.
    On the “SQL Server Browser Properties” page, click the Advanced tab, locate the instance ID in the property list.
    Click OK button.
    Then create an exception for SQL Server 2005 in Windows Firewall.
    Click on Start button, the click on Run and type firewall.cpl, and then click OK. For Windows Vista, type firewall.cpl in Start Search box and press Enter key, then click on Allow a program through Windows Firewall link on left tasks pane.
    In “Windows Firewall”, click the Exceptions tab, and then click Add Program.
    In the “Add a Program” window, click Browse button.
    Click the C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\sqlservr.exe executable program, click Open button. MSSQL.1 with is a placeholder for the instance ID that is obtained from previous procedure. Note that the path may be different depending on where SQL Server 2005 is installed.
    Click OK button.
    Repeat steps 1 through 5 for each instance of SQL Server 2005 that needs an exception.
    For SQL Server Browser service, locate the C:\Program Files\Microsoft SQL Server\90\Shared\sqlbrowser.exe executable program, and click Open button.
    Click OK button.

  • DB Connect from BW on Oracle to MS SQL Server 2005

    Hello,
    I am having issues replicating Meta-Data from SQL server databases via DBCONNECT to SAP BW.
    For instance we have the CCM DB and the Siebel DB.  We can transfer meta-data from CCM with no problem (SQL Server 2000) but we cannot transfer meta-data from Siebel (SQL Server2005).
    Our SAP BW is system is on an Oracle database.
    CCM is on OS Win 2003. SQL 2000 SP4.
    Siebel is on Win 2003 Server Enterprise 5.2 and SQL Server 2005 SP2.
    I already have the dbsl for SQL server installed in the BW system. When I do a Connection Check of the source systems in RSA1, it says "Source system connection OK".
    Any help will be highly appreciated.
    Thanks,
    Ajay

    Hi,
    I don't think the 32 vs. 64 bit is the issue. Have you tried checking OSS note: 512739. It describes the prerequisites for accessing MS SQLServer via DB Connect. Normally problems occurs due to unsupported data types being used in SQLServer - in such cases you have to create views in the source system and then use these views instead of the actual database tables. In the view you can perform the necessary data type conversion.
    Hth,
    Jacob

  • Oracle provider Issue in SQL Server 2005

    Hi all,
    On the dev server, I'm using SSAS 2005 (32-bytes) + Oracle provider for OLE DB to access my Oracle Database and it works perfectly.
    On the production server, SSAS 2005 is running on a 64-bytes platform.
    The Oracle client 10.2.0.1.0 (64 bits) has been installed containing the Oracle provider for OLE DB but unfortunately the Oracle provider for OLE DB does not appear in the list in BIDS when trying to create a date source.
    Could someone help ?
    Regards,
    Juan

    After much grief I figured this out and this works for me going from x64 sql 05 on windows server 2003 to x86 oracle 10g on another windows server 2003 box...
    Software Prerequisites
    •     x64 Oracle Client:
    http://www.oracle.com/technology/software/products/database/oracle10g/htdocs/10201winx64soft.html
    •     x64 Oracle Data Access Components (ODAC) http://www.oracle.com/technology/software/tech/windows/odpnet/64-bit/index.html
    •     x86 Oracle Client:
    http://www.oracle.com/technology/software/products/database/oracle10g/htdocs/10201winsoft.html
    •     SQL Server 2005 SP2 (x64):
    http://www.microsoft.com/downloads/details.aspx?FamilyID=D07219B2-1E23-49C8-8F0C-63FA18F26D3A&displaylang=en
    Patch Level Required (As of Thursday, July 31, 2008):
    •     Microsoft SQL Server Management Studio: 9.00.3042.00
    •     Microsoft Analysis Services Client Tools: 2005.090.3042.00
    •     Microsoft Data Access Components (MDAC): 2000.086.3959.00 (srv03_sp2_rtm.070216-1710)
    •     Microsoft MSXML: 2.6 3.0 4.0 6.0
    •     Microsoft Internet Explorer: 7.0.5730.13
    •     Microsoft .NET Framework: 2.0.50727.42
    •     Operating System: 5.2.3790
    •     Oracle Data Access Components (ODAC): 10.2.0.3.00 (64-bit Oracle10g Release 2 ODAC for Windows x64)
    1. install the x64 and x86 oracle clients on the mssql box
    2. install the odac on the mssql
    3. Verify that the registry settings at
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\MTxOCI and
    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\MSDTC\MTxOCI
    are correct:
    a.     OracleOciLib = oci.dll
    b.     OracleSqlLib = orasql10.dll
    c.     OracleXaLib = oraclient10.dll
    4. Verify that your tnsnames.ora and sqlnet.ora files have the correct info to connect to the source Oracle 10g (x86) 32 bit source. Note if there is a DNS or other name resolution problem in the environment you may need to change your host entry in your tnsnames file to be the actual I.P. address of the source Oracle box, until the network issue is resolved by the applicable environments network engineer. Additionally, note that if your client tnsnames.ora file is not configured to match the network topology in use, you will have issues… loopback configurations particularly cause grief.
    5. Update Machine.config Add the following binding policy:
    <runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
    <dependentAssembly>
    <assemblyIdentity name="Oracle.DataAccess" publicKeyToken="89b483f429c47342" />
    <bindingRedirect oldVersion="2.0.0.0-10.9.9.9" newVersion="2.102.3.2" />
    </dependentAssembly>
    </assemblyBinding>
    </runtime>
    6. Save the following as a *.reg file and run it...
    Windows Registry Editor Version 5.00
    [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\MSDTS\Setup\WizardPath]
    @="C:\\Progra~2\\Microsoft SQL Server\\90\\DTS\\Binn\\DTSWizard.exe"
    7. Save the following as a *.bat file...
    rem Progra~2 is short path name for "Program Files (x86)" and works around an Oracle client bug that doesn't like the ()'s in the path
    start /B "C:\Progra~2\Microsoft Visual Studio 8\Common7\IDE" "C:\Progra~2\Microsoft Visual Studio 8\Common7\IDE\devenv.exe"
    8. Save the following as a *.bat file...
    start /B "C:\Progra~2\Microsoft SQL Server\90\Tools\binn\VSShell\Common7\IDE" "C:\Progra~2\Microsoft SQL Server\90\Tools\binn\VSShell\Common7\IDE\SqlWb.exe"
    9. Create a shortcut that points to each of the batch files you just created and only launch BIDS or SSMS from those *.bat files...
    10. create your packages, etc., as normal, but you will not be able to fully test them from BIDS or SSMS because they are 32 bit running in 64 bit o/s...
    11. Create a job with a line similar to the following as a cmdexec type of job...
    "C:\Progra~2\Microsoft SQL Server\90\DTS\Binn\DTExec.exe" /FILE "C:\SomeWidget.dtsx" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF
    12. your done...
    Best Regards, from a Las Vegas Bohemian...

  • 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?  

  • MS SQL SERVER 2005 Trial Download

    Hi,
    I am planning to install ms sql server 2005 trailer edition in my system
    i want SSIS SSAS SSRS every thing i want (Standard Edition or Enterprise Edition)
    can you please send me currect link MS SQL SERVER installation
    Thanks
    siva

    SQL Server 2005 SP3 Beta is published on the Microsoft web
    Download SQL Server 2005 SP3
    What's New in SQL Server 2005 SP3
    and SQL Server 2005 SP2 is available at:
    http://www.microsoft.com/Sqlserver/2005/en/us/
    Dannol

  • BPC 5.1 SP11 with SQL SERVER 2005 SP3

    Hi all,
    i have a BPC 5.1 SP11 single-server installation.
    I know the DB Server prerequisite is Microsoft SQL Server 2005 SP2 and cumulative update package 8.
    SQL Server 2005 SP3 is supported?
    is there any document about compatibility?
    have i install SP3 before or after BPC Installation?
    thanks

    HI Paolo,
    SQL Server 2005 SP3 is supported with SAP BPC 5.1 SP3 or any other later version.
    We already installed for few customers SP3 and this patch fix bugs into SSAS and also improve some performances regarding SSAS.
    So the recommendation will be to apply this patch in your environment because it will bring just benefits.
    If you have multiserver installation remmeber that you have to apply the patch in all servers not just into Database server.
    Regards
    Sorin Radulescu

  • Unable to Access SQL Server 2005 Remotedly

    Not sure if this is the right forum to post this...
    After going through lot of old posts in various forums and changing lot of settings, i'm still not able to access my Server remotely.
    This is Windows 2003 Server machine with Sonicwall Firewall, i have allowed Port 1433 in both Firewall and ISA and call is getting through but i'm getting following error msg :-
    {"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. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)"}
    This machine is also having Sql Server 2000, and the SQL Server 2005 is installed with named instance.
    My connection string is :-
    "Data Source=192.168.0.1\MYSERVER;Initial Catalog=MyDatabase;Integrated Security=True"
    In example above, i'm showing dummy values but actual string is having the actual live IP address and correct named instance and database.
    If i use a local address like 192.168.0.1 then i'm able to connect.
    My TCP/IP Address in Sql configuration is having my Live IP Address and the port 1433.
    Any help will be highly appreciable..

    i'm still checking on this. i have changed the port now to 1434 and changed in all places.
    my connection string is also changed now, so now i'm using :- MYIP\MYSERVER,1434
    now i'm getting a different error msg
    {"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. (provider: TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.)"}
    this can also be due to firewall or something else is blocking it, i will rechk n post back final answer.

  • SQL Server 2005 performance decreases with DB size while SQL Server 2012 is fine

    Hi,
    We have a C# windows service running that polls some files and inserts/updates some fields in database.
    The service was tested on a local dev machine with SQL Server 2012 running and performance was quite decent with any number of records. Later on the service was moved to a test stage environment where SQL Server 2005 is installed. At that point database
    was still empty and service was running just fine but later on, after some 500k records were written, performance problems came to light. After some more tests we've founds out that, basically, database operation performance in SQL Server 2005 decreases with
    a direct correlation with the database size. Here are some testing results:
    Run#
    1
    2
    3
    4
    5
    DB size (records)
    520k
    620k
    720k
    820k
    920k
    SQL Server 2005
    TotalRunTime
    25:25.1
    32:25.4
    38:27.3
    42:50.5
    43:51.8
    Get1
    00:18.3
    00:18.9
    00:20.1
    00:20.1
    00:19.3
    Get2
    01:13.4
    01:17.9
    01:21.0
    01:21.2
    01:17.5
    Get3
    01:19.5
    01:24.6
    01:28.4
    01:29.3
    01:24.8
    Count1
    00:19.9
    00:18.7
    00:17.9
    00:18.7
    00:19.1
    Count2
    00:44.5
    00:45.7
    00:45.9
    00:47.0
    00:46.0
    Count3
    00:21.7
    00:21.7
    00:21.7
    00:22.3
    00:22.3
    Count4
    00:23.6
    00:23.9
    00:23.9
    00:24.9
    00:24.5
    Process1
    03:10.6
    03:15.4
    03:14.7
    03:21.5
    03:19.6
    Process2
    17:08.7
    23:35.7
    28:53.8
    32:58.3
    34:46.9
    Count5
    00:02.3
    00:02.3
    00:02.3
    00:02.3
    00:02.1
    Count6
    00:01.6
    00:01.6
    00:01.6
    00:01.7
    00:01.7
    Count7
    00:01.9
    00:01.9
    00:01.7
    00:02.0
    00:02.0
    Process3
    00:02.0
    00:01.8
    00:01.8
    00:01.8
    00:01.8
    SQL Server 2012
    TotalRunTime
    12:51.6
    13:38.7
    13:20.4
    13:38.0
    12:38.8
    Get1
    00:21.6
    00:21.7
    00:20.7
    00:22.7
    00:21.4
    Get2
    01:38.3
    01:37.2
    01:31.6
    01:39.2
    01:37.3
    Get3
    01:41.7
    01:42.1
    01:35.9
    01:44.5
    01:41.7
    Count1
    00:20.3
    00:19.9
    00:19.9
    00:21.5
    00:17.3
    Count2
    01:04.5
    01:04.8
    01:05.3
    01:10.0
    01:01.0
    Count3
    00:24.5
    00:24.1
    00:23.7
    00:26.0
    00:21.7
    Count4
    00:26.3
    00:24.6
    00:25.1
    00:27.5
    00:23.7
    Process1
    03:52.3
    03:57.7
    03:59.4
    04:21.2
    03:41.4
    Process2
    03:05.4
    03:06.2
    02:53.2
    03:10.3
    03:06.5
    Count5
    00:02.8
    00:02.7
    00:02.6
    00:02.8
    00:02.7
    Count6
    00:02.3
    00:03.0
    00:02.8
    00:03.4
    00:02.4
    Count7
    00:02.5
    00:02.9
    00:02.8
    00:03.4
    00:02.5
    Process3
    00:21.7
    00:21.0
    00:20.4
    00:22.8
    00:21.5
    One more thing is that it's not Process2 table that constantly grows in size but is Process1 table, that gets almost 100k records each run.
    After that SQL Server 2005 has also been installed on a dev machine just to test things and we got exactly the same results. Both SQL Server 2005 and 2012 instances are installed using default settings with no changes at all. The same goes for databases
    created for the service.
    So the question is - why are there such huge differences between performance of SQL Server 2005 and 2012? Maybe there are some settings that are set by default in SQL Server 2012 database that need to be set manually in 2005?
    What else can I try to test? The main problem is that production SQL Server will be updated god-knows-when and we can't just wait for that.
    Any suggestions/advices are more than welcome.

    ...One more thing is that it's not Process2 table that constantly grows in size but is
    Process1 table, that gets almost 100k records each run....
    Hi,
    It is not clear to me what is that you are doing, but now we have a better understanding on ONE of your tables an it is obviously you will get worse result as the data become bigger. Actually your table look like a automatic build table by ORM like Entity
    Framework, and it's DDL probably do not much your needs. For example if your select query is using a filter on the other column that [setID] then you have no index and the server probably have to scan the entire table in order to find the records that you
    need.
    Forum is a suitable place to seek advice about a specific system (as I mentioned before we are not familiar with your system), and it is more suitable for general questions. For example the fact that you have no index except the index on the column [setID]
    can indicate a problem. Ultimately to optimize the system will need to investigate it more thoroughly (as it is no longer appropriate forum ... but we're not there yet). Another point is that now we can see that you are using [timestamp] column, an this
    implies that your are using this column as a filter for selecting the data. If so, then maybe a better DDL will be to use clustered index on this column and if needed a nonclustered index on the [setID] if it is needed at all...
    what is obviously is that next is to check if this DDL fit
    your specific needs (as i mentioned before).
    Next step is to understand what action do you do with this table. (1) what is your query which become slowly in a bigger data set. (2) Are you using ORM (object relational mapping, like Entity Framework
    code first), and if so then which one.
    [Personal Site] [Blog] [Facebook]

  • How to attached a sql server 2008 database on sql server 2005

    Hi,
    I have a backup of database designed over sql server 2008. I need to attacched this on a machine where sql server 2005 is installed and I am getting the message while attaching the database.
    "The database can not be opened because it is version 661.
    the server supports version 611 and earlier"

    You need to install/have another instance of SQL Server 2008, restore over there the database and perhaps create a SSIS package to move objects and data into SQL Server 2005
    Best Regards,Uri Dimant SQL Server MVP,
    http://sqlblog.com/blogs/uri_dimant/
    MS SQL optimization: MS SQL Development and Optimization
    MS SQL Consulting:
    Large scale of database and data cleansing
    Remote DBA Services:
    Improves MS SQL Database Performance
    SQL Server Integration Services:
    Business Intelligence

Maybe you are looking for

  • How can I pass field value beetwen view in IC Web Clien

    Hi my name is Adrian and I am begining abuot BSPs programming. I have a next problem, I have two views, IRecReson.htm and IRecFollowUp.htm.  They have a description field both, and I need to pass the same value to description field when the user save

  • Images missing in LR 4.6 catalog

    I opned lightroom 4.6 yesterday and the raw files i had been working on are missing from the catalog? How can this be? They are no longer on my CF card so I cannot reload from there.

  • Adobe LMservice causing logging off problems

    When shutting down or loggin off Windows XP srvc Pck3, I keep getting this error message: End Program-1184, 136c, dsagent.exe (it changes everytime I logg off) and it only happens with my user. I have performed a "clean boot" and I have isolated the

  • SQL Expression returning too many results

    I am trying to display the value of a field in one table as a caption in the report header. This  caption is above a u2018descriptionu2019 field in the details section. When I run my report, I get  the description field displaying 832 times; which is

  • Re-Using Java Business Layer in Flex

    I am new to flex and particulalry looking at this to use as front end for existing Web based Java Application as front end. We have comprehensive business layer written using POJOs and DAOs and want to reuse it. I will be using remote objects to call