SQL server 2005 Clients Tools

hI Folks,
I'm trying to install Enterprise Manager on my 64 bit laptop,
but I get an error message saying its not suppported on the current
processor type.
Are there any other versions about that will work?
Is there another way I can query my SQL db?
Thanks
Matt

SQL 2005 should be using SQL Server Manager Studio that comes
with SQL 2005. Not sure if the old SQL 2000 Enterprise manager
works with x64.

Similar Messages

  • Can't Uninstall SQL Server 2005 Express Tools

    I am attempting to install SQL Server 2008 Enterprise Trial and receive the follow error during installation.
    "The SQL Server 2005 Express Tools are installed. To continue, remove the SQL Server 2005 Express Tools."
    I have used Add or Remove programs to remove all components of SQL Server 2005 Express.  I have even reinstalled the Workstation Tools of SQL Server 2005 just so I could indiviually remove those tools, and then completly removed the SQL 2005 installation.
    I have used regedit to search for any instance of SQL Server 2005, there is none.
    There is still an entry for SQL Server Mangement Express in my all programs listing.  However trying to launch that program fails with errors, so it is partial still installed.
    Can anyone tell me how to wipe out these last bits of SQL Server 2005 Express Tools?  I have tried everything I have found searching this forum to no avail.
    Bill

    Renaming or deleting the registry key was the only solution for me. It is not eough to rename a sub-key, I found you must rename or remove the key at the level of "\90"
    HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\90
    I have not tried every permutation but these are the previous steps in order that were NOT helpful.
    Sometimes it is good to know what has been tried and does not work, so you do not spend time in dead ends.
    These do NOT work
    1. resolution at this link did not work for me although it worked for that person
    "rename registry key "
    http://jasonfollas.com/blog/archive/2008/06/19/sql-server-2008-rc0-install-sql2005ssmsexpressfacet.aspx
    rename key from: HKLM\Software\Microsoft\Microsoft SQL Server\90\Tools\ShellSEM
    to: ShellSEM.old
    (If I had renamed \90 it might have succeeded)
    2. solution at this link did not work for me although it worked for that person
    "changing the Regional Settings of my computer"
    http://www.kodyaz.com/blogs/software_development_blog/archive/2008/02/22/840.aspx
    3. reset.cmd
    download and execute reset.cmd to reset many registry settings
    Nope, no luck
    4. download entire 2008 express package as an ISO file in the small chance any previous files were corrupted.
    The ISO image was 744 meg, which can only be burned onto a double-layer disk.
    Then I remembered I don't have a double-layer burner.
    Duh.
    5. removing 3rd party tools
    - Remove SQL Server 2005 Express Tools
    - Remove Red-Gate SQL Prompt if installed.
    http://blog.crowe.co.nz/archive/2008/08/14/quotThe-SQL-Server-2005-Express-Tools-are-installed.-To-continue.aspx
    mainly because neither were actually listed in add/remove programs, nor was Red Gate in the registry
    (or redgate, red-gate, red_gate)
    6. "Solving setup errors by using the SubInACL tool to repair file and registry permissions"
    http://blogs.msdn.com/astebner/archive/2006/09/04/739820.aspx
    7. rename the instance of SQL Server 2008 when installing
    Nope.
    8. With Add/remove programs, remove
    - sql server 2005
    - anything else that had in the title "sql server 2005"
    - sql server system clr types (which sounded sort of like a 3-rd party tool and I had not used it in a year)
    - remove folder
    c:\program files\microsoft\Microsoft SQL Server90
    Nope, no luck
    10. With a Microsoft tool "Windows Install Clean Up" inspect any add/remove programs that were removed and absolutely remove their install logs
    Nope.  So it was not due to any residual information from SQL Server 2005
    11. With Add/remove programs, remove
    - anything that has the title sql server 2008
    and try to re-install, which did not work.
    Finally found this thread and deleted the key and the installation succeeded.
    It did not take 2 days, but almost.
    This is a test, right? We have to navigate all the half-good information and actually succeed installing SQL Server 2008 then we earn the privilege to use it?  Yay!

  • MS SQL SERVER 2005 CLIENT ACCESS TOOLS

    HELLO EXPERTS
    I wanted to install sql 2005 client  access tools, but I cannot seem to find it on my installation CD, any help please? Urgent and thank you

    Its called Management Tools when you run it from installaton cd.
    see
    http://it-n-careerz.blogspot.in/2013/04/how-to-install-sql-server-management.html
    Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

  • SQL Server 2005 Installation Error

    I am installine ECC6 on SQL Serer 2006. I have started the SQL Server installation, using the SQL4SAP.vbs and after about 10 minutes the installation stops with an error. I am pointed to a fine Summary.txt but the details in the file do not give a clue on the problem:
    Machine         : SAPDEMO
    Product         : SQLXML4
    Product Version : 9.00.1399.06
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_SQLXML4_1.log
    SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt.
    Time            : Mon Dec 03 09:09:38 2007
    List of log files:
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_Core(Local).log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_SQLSupport_1.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_SQLNCLI_1.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_OWC11_1.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_SqlWriter_1.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_BackwardsCompat_1.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_MSXML6_1.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_SQLSupport_2.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_SQLNCLI_2.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_OWC11_2.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_BOL_1.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_BackwardsCompat_2.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_SQLXML4_1.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_Datastore.xml
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_.NET Framework 2.0.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_Core.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_.NET Framework 2.0 LangPack.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_.NET Framework Upgrade Advisor.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_.NET Framework Upgrade Advisor LangPack.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_.NET Framework Windows Installer.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_.NET Framework Windows Installer LangPack.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_SNAC.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_Support.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_SCC.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_WI.log

    Hi Rajeev,
    Indeed it was a typo error I am attempting SQL Server 2005.
    I am using the 32 bit installation, that has been checked.
    Here are the details from C:\Windows\SQL4SAP.log
    Customized installation of SQL Server 2005 for SAP *
    Log File: C:\WINDOWS\SQL4SAP.log
    Script started 03/12/2007 08:46:25 on SAPDEMO
    System settings:
      Win32_Processor.Name=Intel(R) Core(TM)2 Duo CPU     T7500  @ 2.20GHz
      Win32_Processor.Name=Intel(R) Core(TM)2 Duo CPU     T7500  @ 2.20GHz
      Win32_ComputerSystem.SystemType=X86-based PC
      Win32_OperatingSystem.OSType=18
      Win32_OperatingSystem.Version=5.2.3790
      Win32_OperatingSystem.ServicePackMajorVersion=2
      Win32_OperatingSystem.Caption=Microsoft(R) Windows(R) Server 2003, Standard Edition
      Win32_OperatingSystem.ProductType=3
      Win32_OperatingSystem.OSProductSuite=272
      Win32_OperatingSystem.OSLanguage=1033
    Windows version:
      OSVersion         = 5.2
      OSFamily          = Windows2003
      OSServicePack     = 2
      OSEdition         = Server
      OSSystemType      = X86
      OSProductSuite    = Terminal Server
      OSMsiVersion      = 3.1.4000.4042
      OSMdacVersion     = 2.82.3959.0
      OSLanguage        = English – United States
      OSLanguageID      = 1033
    Environment on SAPDEMO:
      userDir           = C:\Documents and Settings\Administrator\
      tmpDir            = C:\DOCUME1\ADMINI1\LOCALS~1\Temp\1\
      rootDir           = C:\WINDOWS\
      prgDir            = C:\Program Files\
      prgDirX86         = \
    SQL4SAP version:
      version:          ' v3.2.44    Mar 2007: SQL2005 SP2, Windows2003 SP2
      size:             86124
      created:          30/11/2007 16:59:31
      modified:         20/03/2007 13:36:44
      exe:              C:\WINDOWS\system32\cscript.exe
      script:           C:\SAP_CD\CD2\SQL4SAP.vbs
      C:                C:
    Script path:
      myRoot            = C:\SAP_CD\CD2\
      myDir             = C:\SAP_CD\CD2\x86\
      myDirUNC          = C:\SAP_CD\CD2\x86\
    Script settings:
      SqlAuthInstall    = False
      SilentInstall     = False
      DeEditionOnly     = False
      DeEditionPossible = False
      SapItMsgBox       = False
      SilentRtmSetup    = True
    Service Account:
      "C:\SAP_CD\CD2\x86\SqlCmd\GetSidName.exe" S-1-5-18 =>NT AUTHORITY\SYSTEM
      OSSystemAccount= NT AUTHORITY\SYSTEM
    03/12/2007 08:46:28
    Input Box "Select SQL Server instance"
    No SQL Server instance was found.
    SQL Server Native Client               not installed
    SQL Server 2005 Client Tools           not installed
    Enter a new or existing instance name.
    - for a Default Instance, enter:     (default)   or   .
    - for a Named Instance, enter:       <SID>
    To install SQL Client Tools Only, press Cancel.
    Result: (default)
    Registry settings (1/2):
    HKLM\SOFTWARE\Microsoft\DataAccess\FullInstallVer
    READ: 2.82.3959.0
    HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\{3d06c673-5e8a-41c0-b47f-3c3ca0a22e67}
    READ: 4
    HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\{3d06c673-5e8a-41c0-b47f-3c3ca0a22e67}
    WRITE(REG_DWORD): 4
    HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\{319b29ae-7427-4fbc-9355-22df056c27a4}
    READ: 4
    HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\{319b29ae-7427-4fbc-9355-22df056c27a4}
    WRITE(REG_DWORD): 4
    HKLM\SOFTWARE\Microsoft\Microsoft SQL Native Client\CurrentVersion\Version
    READ:
    HKLM\SOFTWARE\Microsoft\Microsoft SQL Native Client\CurrentVersion\PatchLevel
    READ:
    HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\90\Tools\ClientSetup\CurrentVersion\CurrentVersion
    READ:
    HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\90\Tools\ClientSetup\CurrentVersion\CSDVersion
    READ:
    03/12/2007 08:46:32
    Message Box "Confirmation"
    You have chosen to install the new instance
    SQL Instance:       (default)
    SQL Version:        9.00.3042
    SQL Edition:        2005 Enterprise Edition
    SQL Collation:      SQL_Latin1_General_CP850_BIN2
    Authentication:     Windows only
    Login sa:           random password, login disabled
    =======================================
    The installation may take 15 minutes or longer
    =======================================
    Do you want to start the installation now?
    Result: vbOK
    03/12/2007 08:46:34
    installing SQL Server 2005 Enterprise Edition on X86 - build 9.00.1399 ...
      Log File:    C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt
      Command:     "C:\SAP_CD\CD2\x86\EnterpriseEdition\Servers\setup.exe" /qn USERNAME="SAP ISV Royalty Licensing Program" ADDLOCAL=Connectivity,SQL_Tools90,SQLXML,Tools_Legacy,SQL_Documentation,SQL_BooksOnline,SQL_Data_Files,SQL_FullText PERSEAT=50 INSTANCENAME=MSSQLSERVER SQLCOLLATION=SQL_Latin1_General_CP850_BIN2 AGTAUTOSTART=1 SQLACCOUNT="NT AUTHORITY\SYSTEM" AGTACCOUNT="NT AUTHORITY\SYSTEM" SQLBROWSERACCOUNT="NT AUTHORITY\SYSTEM" DISABLENETWORKPROTOCOLS=0 SAPWD=xxxxxxxxxxxxxxxx
      Return Code: 1605
    03/12/2007 08:48:41
    Log file C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt
    Microsoft SQL Server 2005 9.00.1399.06
    ==============================
    OS Version      : Microsoft Windows Server 2003 family, Standard Edition Service Pack 2 (Build 3790)
    Time            : Mon Dec 03 08:46:48 2007
    Machine         : SAPDEMO
    Product         : Microsoft SQL Server Setup Support Files (English)
    Product Version : 9.00.1399.06
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SQLSupport_1.log
    Machine         : SAPDEMO
    Product         : Microsoft SQL Server Native Client
    Product Version : 9.00.1399.06
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SQLNCLI_1.log
    Machine         : SAPDEMO
    Product         : Microsoft SQL Server VSS Writer
    Product Version : 9.00.1399.06
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SqlWriter_1.log
    Machine         : SAPDEMO
    Product         : Microsoft SQL Server Setup Support Files (English)
    Product Version : 9.00.1399.06
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SQLSupport_2.log
    Machine         : SAPDEMO
    Product         : Microsoft SQL Server Native Client
    Product Version : 9.00.1399.06
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SQLNCLI_2.log
    Machine         : SAPDEMO
    Product         : Microsoft SQL Server 2005 Books Online (English)
    Product Version : 9.00.1399.06
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_BOL_1.log
    Machine         : SAPDEMO
    Product         : SQLXML4
    Product Version : 9.00.1399.06
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SQLXML4_1.log
    SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt.
    Time            : Mon Dec 03 08:48:39 2007
    List of log files:
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_Core(Local).log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SQLSupport_1.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SQLNCLI_1.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SqlWriter_1.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_MSXML6_1.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SQLSupport_2.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SQLNCLI_2.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_BOL_1.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SQLXML4_1.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_Datastore.xml
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_.NET Framework 2.0.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_Core.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_.NET Framework 2.0 LangPack.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_.NET Framework Upgrade Advisor.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_.NET Framework Upgrade Advisor LangPack.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_.NET Framework Windows Installer.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_.NET Framework Windows Installer LangPack.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SNAC.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_Support.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SCC.log
    service MSSQLSERVER does not exist
    03/12/2007 08:48:41
    Message Box "Installation failed"
    The unattended installation failed.
      Installation Step: SQL Server - build 9.00.1399
      Return Code:       1605
      Log File:          C:\WINDOWS\SQL4SAP.log
    Check the log file above!
    See also SAP note 896566 for known issues
    Result: vbOK
    Registry settings (2/2):
    HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names\SQL\MSSQLSERVER
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg0
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg1
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg2
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg3
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg4
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg5
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg6
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg7
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg8
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg9
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg10
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg11
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg12
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg13
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg14
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg15
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg16
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg17
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg18
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg19
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg20
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLSERVER\Setup\SQLPath
    READ:
    HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\{3d06c673-5e8a-41c0-b47f-3c3ca0a22e67}
    WRITE(REG_DWORD): 4
    HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\{319b29ae-7427-4fbc-9355-22df056c27a4}
    WRITE(REG_DWORD): 4
    03/12/2007 08:48:47
    Quit script with return code 1

  • XL Reporter on SBO2005 SP1 PL10 & MS SQL Server 2005

    Hi All,
    Has any1 installed XL Reporter on SBO 2005 SP1 that has MS SQL Server 2005???
    I keep getting an error....
    "Unable to connect to XL Reporter....
    User Authentication Failed.
    ......SQL Server does not exist or access is denied. Cant connect to database provider ........"
    Thanks.

    Hi Noor
    I'm pasting the SAP note for you:
    TCP/IP might not be enabled in the SQL Server Configuration Manager
    1.Properties for SQL server selected  to allow SQL server &
    Windows authentication.
    - To do this: In SQL server Management studio-Right click on Server -Properties - Security -
    choose Allow SQL server & Windows authentication
    2. Under Microsoft SQL Server 2005 -> configuration tools ->
    Configuration Manager - client protocols - enable the tcp/ip
    3.In SQL server configuration manager  SQL server 2005 Network configuration - enable the TCP/IP
    4. In SQL Server 2005 Surface Area Configuration
    - Surface Area Configuration for services and connections
    - Expand SQL 2005 - Database Engine - Remote Connections
    - Choose Local and remote connections and select using both TCP/IP nad named pipes
    5. In SQL Server Management Studio -> Right click on the server instance -> stop the service and start again.
    Hope this helps
    Daan

  • Addon in Client is not connecting to SQL Server 2005

    Hi, we have an add-on, which is working in SBO 2005 with SQL Server 2000.
    When the addon tries to connect to the same DB, restored on a SQL Server 2005, the addon is hanging up on the oCompany.Connect method. But this only happens when we try a remote connection from a SBO client.
    If we run the addon from the SBO server, where the SQL Server is running too, the addon completes the connection in the expected way.
    The SBO Client is connecting to the server, and works fine, but the addon is not connecting to the server.
    We try to connect to the server from the client, using SQL Query Analizer from SQL Server 2000, and it works fine too.
    Does anyone knows how to fix this issue?
    Thanks

    Hi Alejandro, thanks for your response.
    After installing SBO Patch 20 the add-on is now connecting fine, so I think it must be an upgrade on the new DI API. I noticed the version changes from 6.80.318 to 6.80.319
    I had checked the SQL to confirm is was allowing remote connections.
    Thank you guys.

  • Driver's SQLSetConnectAttr failed/SQL Server 2005/ODBC Native Client

    I have an ODBC application that I am writing in VS 2008 C++. I freely admit to not being an ODBC expert. I am having trouble with SetConnectAttr failures. I've got them down to one specific case that I will describe here. The environment is 64-bit Windows
    7 (client) and SQL Server 2005 running on Win Server 2003. I am using a 32-bit ODBC connection. For the most part the application is working: I am successfully using the connection to do multiple INSERTs into multiple tables. I get lots of hits when I
    search on the above error message but they are so "all over the map" (Oracle, packaged applications, specific situations) that I have not been able to find one that seems to apply. Connection Pooling is not turned on in the connection.
    I make the following call
    SQLUINTEGER timeout = 10;
    // seconds
    retCode = SQLSetConnectAttr(ConnectionHandle, SQL_ATTR_LOGIN_TIMEOUT, &timeout, 0);
    I receive a zero in retCode.
    However when I subsequently issue the SQLConnect() I receive
    [Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed
    I was setting three different connection attributes and getting the above message twice, but I have for debugging purposes commented out two of the set's. The above call is the only attribute I am setting so it is apparently the one that is failing. Any
    help would be appreciated.
    Charles

    In case anyone else runs into this, here is the real problem with the original code:
        retCode = SQLSetConnectAttr(ConnectionHandle, SQL_ATTR_LOGIN_TIMEOUT,
    &timeout, 0);
    The SQL_ATTR_LOGIN_TIMEOUT attribute takes an integer by value, not a pointer to an integer.  This is a confusing aspect of this API.  If you pass a pointer, ODBC is really "seeing" a large integer value, which causes the
    code to effectively behave as though there were an infinite timeout.
    Instead, just pass the value of the timeout:
        retCode = SQLSetConnectAttr(ConnectionHandle, SQL_ATTR_LOGIN_TIMEOUT,
    (SQLPOINTER) timeout, SQL_IS_UINTEGER);
    Then the timeout value should be respected.  Using SQLSetConnectOption(SQL_LOGIN_TIMEOUT) seems to be equivalent to the above, provided you pass the timeout by value and not via a pointer.

  • Client transport  between SAP on Oracle 10G and MS SQL server 2005

    Hi Folks,
    We have a requirement where we have to do client export/import from SAP ECC 6.O running on Oracle 10g and to SAP ECC 6.0 running on MS SQL server 2005.I want to know whether SAP supports this and patch levels of all components two systems should be the same.
    Thanks in advance,
    Basis Admin

    Not recommendet because of potential :
    -  patch level inconsistency
    - ABAP dictionary inconsistency (programs, tables)
    - possible client independent configuration conflicts
        existing config cen disturb "imported" client
        imported config can ddisturb  existing clients
    If there are any inconsistencies mentioned above you are in trouble...
    regards,
    wojtek

  • MS-SQL Server 2005 SP1 vs MS-SQL Native Client 2008 or 2012

    Hello,
    I woud like to know if it's possible to use on a computer Windows Seven, the MS-SQL Native Client 2008 or 2012, and connect it on a MS-SQL Server 2005 (under Windows 2003 enterprise).
    Regards,

    Hello,
    Yes, the SQL Server Native client is backward compatible, means you can use Client 2008 or higher to connect to a SQL Server 2005.
    With some limitations the client is also forward compatible, means you can use a client 2005 to connect to SQL Server 2008 and higher; but the client isn't aware of new server features.
    Olaf Helper
    [ Blog] [ Xing] [ MVP]

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

  • SQL Server Error when tryingt to install the CMS DB on SQL Server 2005 x64

    I am trying to install BOEXI R3 on w2k3 64-bit OS in a SQL Server 2005 x64 database, I am currently at the installation step where i Specify an exisiting CMS database. I created a System DSN and tested it, and it was successful. So when I got to the screen where I select my datasource I had to check use trusted connection because the datasource would not show up when Use DSN created by WOW64 option was checked. From there I could select the database I created. Oh yeah, I also made the application server local system account part of my DB admins group so it has full access to the database yet when I click next to connect I get a CMS Database Error: STU000226. here is what I have in my log:
    ThreadID     Message
    (Thu Apr 23 20:57:46 2009)     3024     3028     trace message: findDFA_LLR:  (CmdLineDir) C:Documents and SettingsgsdadminDesktopBOEXI and BSM AnalyticsBOEXI R3 Full Version from SAPpackagedbcheck
    sqlrule.llr
    (Thu Apr 23 20:57:46 2009)     3024     3028     trace message: Loading: database subsystem only
    (Thu Apr 23 20:57:46 2009)     3024     3028     trace message: loading libary succeeded
    (Thu Apr 23 20:57:46 2009)     3024     3028     trace message: DatabaseSubsystem::Init()
    (Thu Apr 23 20:57:46 2009)     3024     3028     (.wireobinit.cpp:96): trace message: Creating the shared CWireObject::PropertyNameMap
    (Thu Apr 23 20:57:46 2009)     3024     3028     (.wireobinit.cpp:118): trace message: Setting static property map
    (Thu Apr 23 20:57:46 2009)     3024     3028     (.wireobinit.cpp:125): trace message: CWireObject::InitializeStaticPropertyMap() - reference count: 1
    (Thu Apr 23 20:57:46 2009)     3024     3028     trace message: initializing subsystem succeeded
    (Thu Apr 23 20:57:46 2009)     3024     3028     trace message: Loading: done loading subsystem - database subsystem only
    (Thu Apr 23 20:57:46 2009)     3024     3028     trace message: DatabaseSubsystem::Connect()
    (Thu Apr 23 20:57:46 2009)     3024     3028     (.DBConnectionManager.cpp:802): trace message: DBConnectionManager - Setting total target number of connections for pool 0 to 1.
    (Thu Apr 23 20:57:46 2009)     3024     3028     (.SQLServerDatabase.cpp:119): trace message: SQLServer error found:  ErrorMessage( (Microsoft)[ODBC Driver Manager] Data source name not found and no default driver specified), ErrorCode(0)
    (Thu Apr 23 20:57:46 2009)     3024     3028     (.dbutils.cpp:820): trace message: Caught DatabaseSubystem Error: BusinessObjects Enterprise CMS: Unable to connect to the CMS system database "BOEXI_CMS". Reason:  (Microsoft)[ODBC Driver Manager] Data source name not found and no default driver specified
    (Thu Apr 23 20:57:46 2009)     3024     3028     trace message: DatabaseSubsystem::Shutdown()
    (Thu Apr 23 20:57:46 2009)     3024     3028     (.wireobinit.cpp:175): trace message: CWireObject::TerminateStaticPropertyMap() - reference count: 1
    (Thu Apr 23 20:57:46 2009)     3024     3028     (.wireobinit.cpp:182): trace message: Releasing
    static property map
    How do I get past this?

    The workaround was, I installed the SQL Server Client tools and created a System DataSource  and then had to create a user DataSource  (it is a quirk in the installer I guess) to get past this point in the installation. Now I have an even bigger problem. Everything but the CMS installed and the installer hung at the "Configuring the CMS" part. The installation finished but when I tried to log into the Central managment console I got this error:
    Error: Server GSD-RRPT-RDC:6400 not found or server may be down (FWM 01003) null
    I looked at the forums for the cause of this error and came to the conclusion that BOEXI does not support an installation on SQL Server 2005 when using Integrated Authentication to the SQL Server. See the engineers here disabled SQL Authentication for the SQL Server and  will not allow it.
    Is this true? Or is there a workaround to install the CMS using Integrated Authentication in the DataSource ?
    Thanks.

  • Transact-SQL debugger not working in SQL Server 2008: "...debugger does not support SQL Server 2005 or earlier..."

    I have recently installed SQL Server 2008. When I try to execute a query against an Access database, I receive this debugging error:
    "Unable to start Transact-SQL debugger. The Transact-SQL debugger does not support SQL Server 2005 or earlier versions of SQL Server. (SQLEditors)"
    Nor will the query execute; I get a transport-level error 0. Any thoughts?

    Hi Davidmhjr,
    >>Unable to start the Transact-SQL Debugger. The Transact-SQL Debugger does not support SQL Server 2005 or earlier versions of SQL Server. (SQLEditors).
    Have you tried to restart the server once you have installed SQL Server 2008? As Naomi N mentioned please check the version of SQL Server you are using.
    If you tried to connect to SQL Server 2005 from SQL Server 2008 SSMS, you would not be able to debug and get this error, it happens because T-SQL debugger includes both server-side and client-side components. The server-side debugger components are installed
    with each instance of the SQL Server 2008 Database Engine. The client-side components are installed when you install the SQL Server 2008 client-side tools.
    So it works with SQL Server 2008 only so far. Another way is you can triy to use SQL Server 2005 SSMS to connect to SQL Server 2005.
    More information about configuration requirement to run T-SQL debugger as below, please refer:
    There are no configuration requirements to run the Transact-SQL debugger when SQL Server Management Studio is running on the same computer as the instance of the SQL Server Database Engine. However, to run the Transact-SQL debugger when SQL Server Management
    Studio is running on a different computer from the instance of the Database Engine, you must enable program and port exceptions by using the Windows Firewall Control Panel application on both computers.
    On the computer that is running the instance of the Database Engine, in Windows Firewall, specify the following information:
    •Add TCP port 135 to the exceptions list.
    •Add the program sqlservr.exe to the exceptions list. By default, sqlservr.exe is installed in C:\Program Files\Microsoft SQL Server\MSSQL10.InstanceName\MSSQL\Binn, where InstanceName is MSSQLSERVER for the default instance, and the instance name for
    any named instance.
    •If the domain policy requires network communications to be done through IPsec, you must also add UDP port 4500 and UDP port 500 to the exception list.
    On the computer that is running SQL Server Management Studio, in Windows Firewall, specify the following information:
    •Add TCP port 135 to the exceptions list.
    •Add program ssms.exe (SQL Server Management Studio) to the exceptions list. By default, ssms.exe is installed in C:\Program Files\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE.
    Hope it is helpful.
    Regards, Amber zhang

  • 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 Memory Explosions

    We have the following configuration:
    ESXi 5.1.0 running on three clustered Dell 710 servers
    vCenter Server 5.1.0
    The clustered servers have a total of 88G of RAM
    SQL Server 2005 x86 running on a virtual Server 2008 R2 x64. All databases run fine for several days with memory usage seeming at ~25%. Suddenly, the memory consumption
    shoots up to ~98% and we have to reboot the server. This is based on information from the task manager and the measurements in vSphere Client. I understand that the task manager is not an accurate measurement when AWE is active but that’s the best I’ve got
    at the moment.
    Here's what we've done thus far:
    Looked through the logs on the SQL Server and found the following:
    In the System log, Resource-Exhaustion-Detected appeared at the same time but the highest memory consumption was services.exe at 125MB. Doesn’t seem to be the culprit.
    In the Applications log, started getting MSSQLSERVER errors indicating ‘The Server was unable to load the SSL provider needed to login.’ These errors persisted through the downtime.
    In the SQL Server Log File Viewer, we see the following errors, though I’m not sure that they are at all related:
    A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 4464, committed (KB)
    66976, memory utilization: 6%
    (About 4.5 hours later) Warning: the available page file has dropped below 4Mb. It is at this point – seemingly – that the memory usage has jumped up to near 100%.
    The virtual server has 8G of RAM allocated. However, within the vSphere Client, the Memory Granted and the Memory Consumed seem to be at the same value…meaning that
    the consumed value seems to be at 100% under normal operating conditions. Not sure why that is.
    If anyone has any recommendations or areas to look, we would certainly appreciate your assistance! Thanks in advance.
    Tony

    I thank you guys so much for the rapid response! Please forgive the delayed response. All of this is on a DoD network and I cannot post to blogs on government machines. I have to go to a private
    machine. Below is the information you asked for:
    The Max Server Memory is 5.0GB and the Min Server Memory is 0.0GB
    I have PerfMon currently running to try and capture as much information as possible.
    We are getting a few other errors in the SQL Log that has given me some concern:
    Failed Virtual Allocation Bytes: FAIL_VIRTUAL_RESERVE 65536
    Memory Manager  VM Reserverd = 3673288 KB  VM Committed = 55688 KB AWE Allocated = 0 KB  Reserved Memory = 1024
    KB  Reserved Memory In Use = 0 KB
    There is also a series of MEMORYCLERK and CACHESTORE errors following
    The Server was unable to load the SSL provider needed to login. SSL is used…
    o   
    I presume that this is due to the lack of memory to process these SSL request.
    There are indeed several Error: 701, Severity: 17, State: 123
    Below is the system information from SQL Server 2005:
    Microsoft SQL Server Management Studio                   9.00.5324.00
    Microsoft Analysis Services Client Tools                       2005.090.5324.00
    Microsoft Data Access Components (MDAC)                6.1.7601.17514 (win7sp1_rtm.101119-1850)
    Microsoft MSXML                                             
                3.0 6.0
    Microsoft Internet Explorer                                         
    8.0.7601.17514
    Microsoft .NET Framework                                          
    2.0.50727.5477
    Operating System                                           
                6.1.7601
    I run a query SELECT SERVERPROPERTY(‘edition’); and it shows ‘Standard Edition’ rather than ‘Standard Edition (64-bit).’
    We are using Windows Server 2008 R2. I don’t believe that there was an x86 version released but I could be wrong.
    I’ve actually looked at enabling the LPIM but we are on a domain that we have no control over and there are GPOs that make it very difficult if not impossible to gpedit but that is something
    we can certainly look into with the domain owners if you think it might help.
    I just ran the following script in SQL:
    Exec sp_configure ‘AWE’
    The response is  name – awe enabled, minimum – 0, maximum – 1, config_value – 0, run_value – 0
    There is no third party software on this server.
    The Max Server Memory is set to 5GM
    Again, I do appreciate all of your help. Please let me know if I can provide anything further.
    Tony

  • SQL Server 2005 Dev Integration Services Fail

    I've got VS2005 v.8.0.50727.867 (vsvista.050727-8600) on my 64bit Windows 7 box.  I am trying to install SQL Server 2005 Integration Services on this Win7 box so I can load and edit the Win XP SSIS projects that I had on my XP box.  So far I've
    not been able to successfully install the Integration Services with a failed permission on the SQL**DTD.msi file.....I've copied this file locally and tried to run it and it would start but then would give permission error.
    Is there an inherent incompatibility running SSIS projects in SQL Server 2005 on a 64bit Win 7 box?  Worked great on my XP box.
    I've been "upgrading" the SSIS projects to VS2008 since I was able to get SSIS installed. Any ideas what I need to do to get this beast to work?
    TIA
    Harry

    Thanks Alberto
    Microsoft SQL Server 2005 9.00.1399.06
    ==============================
    OS Version      : Professional Service Pack 1 (Build 7601)
    Time            : Mon Aug 25 09:31:30 2014
    DT0315 : Microsoft Internet Information Services (IIS) is either not installed or is disabled. IIS is required by some SQL Server features.  Without IIS, some SQL Server features will not be available for installation. To install all SQL Server features,
    install IIS from Add or Remove Programs in Control Panel or enable the IIS service through the Control Panel if it is already installed, and then run SQL Server Setup again. For a list of features that depend on IIS, see Features Supported by Editions of SQL
    Server in Books Online.
    DT0315 : Failed to find the ASP.Net Version Registration with Microsoft Internet Information Services (IIS).
    Machine         : DT0315
    Product         : Microsoft SQL Server Setup Support Files (English)
    Product Version : 9.00.1399.06
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLSupport_1.log
    Machine         : DT0315
    Product         : Microsoft Office 2003 Web Components
    Product Version : 11.0.6558.0
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_OWC11_1.log
    Machine         : DT0315
    Product         : Microsoft SQL Server 2005 Backward compatibility
    Product Version : 8.05.1054
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_BackwardsCompat_1.log
    Machine         : DT0315
    Product         : Microsoft SQL Server Setup Support Files (English)
    Product Version : 9.00.1399.06
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLSupport_2.log
    Machine         : DT0315
    Product         : Microsoft SQL Server Native Client
    Product Version : 9.00.5000.00
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLNCLI_1.log
    Machine         : DT0315
    Product         : Microsoft Office 2003 Web Components
    Product Version : 11.0.6558.0
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_OWC11_2.log
    Machine         : DT0315
    Product         : Microsoft SQL Server 2005 Backward compatibility
    Product Version : 8.05.1054
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_BackwardsCompat_2.log
    Machine         : DT0315
    Product         : Microsoft SQL Server Setup Support Files (English)
    Product Version : 9.00.1399.06
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLSupport_3.log
    Machine         : DT0315
    Product         : Microsoft SQL Server Native Client
    Product Version : 9.00.5000.00
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLNCLI_2.log
    Machine         : DT0315
    Product         : Microsoft Office 2003 Web Components
    Product Version : 11.0.6558.0
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_OWC11_3.log
    Machine         : DT0315
    Product         : Microsoft SQL Server 2005 Backward compatibility
    Product Version : 8.05.1054
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_BackwardsCompat_3.log
    Machine         : DT0315
    Product         : Microsoft SQL Server Setup Support Files (English)
    Product Version : 9.00.1399.06
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLSupport_4.log
    Machine         : DT0315
    Product         : Microsoft SQL Server Native Client
    Product Version : 9.00.5000.00
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLNCLI_3.log
    Machine         : DT0315
    Product         : Microsoft Office 2003 Web Components
    Product Version : 11.0.6558.0
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_OWC11_4.log
    Machine         : DT0315
    Product         : Microsoft VSS Writer for SQL Server 2012
    Product Version : 11.0.2100.60
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SqlWriter_1.log
    Machine         : DT0315
    Product         : Microsoft SQL Server 2005 Backward compatibility
    Product Version : 8.05.1054
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_BackwardsCompat_4.log
    Machine         : DT0315
    Product         : Microsoft SQL Server Setup Support Files (English)
    Product Version : 9.00.1399.06
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLSupport_5.log
    Machine         : DT0315
    Product         : Microsoft SQL Server Native Client
    Product Version : 9.00.5000.00
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLNCLI_4.log
    Machine         : DT0315
    Product         : Microsoft Office 2003 Web Components
    Product Version : 11.0.6558.0
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_OWC11_5.log
    Machine         : DT0315
    Product         : Microsoft SQL Server 2005 Books Online (English)
    Product Version : 9.00.1399.06
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_BOL_1.log
    Machine         : DT0315
    Product         : Microsoft SQL Server 2005 Backward compatibility
    Product Version : 8.05.1054
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_BackwardsCompat_5.log
    Machine         : DT0315
    Product         : Integration Services
    Error           : Failed to install and configure assemblies C:\Program Files\Microsoft SQL Server\90\DTS\Tasks\Microsoft.SqlServer.MSMQTask.dll in the COM+ catalog. Error: -2146233087
    Error message: Unknown error 0x80131501
    Error description: One or more of the components being installed are already registered as 32 bit components in the target application. You must install the 64 bit versions of the components being installed in a different COM+ application, or delete the existing
    32 bit versions of the components being installed from the target COM+ application prior to attempting install of the 64 bit versions. COM+ applications cannot contain bit neutral components.
    Machine         : DT0315
    Product         : Microsoft SQL Server 2005 Integration Services (64-bit)
    Product Version : 9.00.1399.06
    Install         : Failed
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_DTS.log
    Last Action     : InstallFinalize
    Error String    : Failed to install and configure assemblies C:\Program Files\Microsoft SQL Server\90\DTS\Tasks\Microsoft.SqlServer.MSMQTask.dll in the COM+ catalog. Error: -2146233087
    Error message: Unknown error 0x80131501
    Error description: One or more of the components being installed are already registered as 32 bit components in the target application. You must install the 64 bit versions of the components being installed in a different COM+ application, or delete the existing
    32 bit versions of the components being installed from the target COM+ application prior to attempting install of the 64 bit versions. COM+ applications cannot contain bit neutral components.
    Error Number    : 29549
    Machine         : DT0315
    Product         : SQLXML4
    Product Version : 9.00.1399.06
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLXML4_1.log
    Machine         : DT0315
    Product         : Microsoft SQL Server 2005 (64-bit)
    Product Version : 9.00.1399.06
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQL.log
    Machine         : DT0315
    Product         : SQLXML4
    Product Version : 9.00.1399.06
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLXML4_2.log
    Machine         : DT0315
    Product         : Microsoft SQL Server 2005 Analysis Services (64-bit)
    Product Version : 9.00.1399.06
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_AS.log
    Machine         : DT0315
    Product         : Microsoft SQL Server 2005 Notification Services (64-bit)
    Product Version : 9.00.1399.06
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_NS.log
    Machine         : DT0315
    Product         : Microsoft SQL Server 2005 Tools (64-bit)
    Product Version : 9.00.1399.06
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_Tools.log
     SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt.

Maybe you are looking for