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
Similar Messages
-
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
MattSQL 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. -
Sql server - 2005 - Data Protection Tool
Hi,
We are looking any Data Security tool for out existing Data for Protection, we would like to do the Data Encryption and Data masking with some user activity reporting.
Anyone know any good tool?
Right now we are looking tool which one has minimal application rewriting or code changes.
Thanks,Those features were added in SQL Server and weren't available in 2005. Except EFS and Bitlocker which are implementations outside SQL Server.
Tibor Karaszi, SQL Server MVP |
web | blog -
Installation of SQL Server device client accesses
Hello,
Please help me out for the below query.
Actually I don't have an idea of User & Device CAL Licenses. I joined newly in a company as SQL DBA but I don't know about the licensing part. So, In my present company they are having SQL Server 2008 R2 Standard Edition with 5 SQL Device CAL's. I need
to install device CAL's for the Developers. I had checked in Licensing details. So, it is showing 5 SQL Device CAL's. When I go to download it is showing many files and basically it is not showing the CAL application. I need to know which file exactly I should
download and install. All applications are showing the same but it is not confirming about the device CAL Application.
Kindly let me know which file I need to download and install and how to manage device cal licenses. I searched in internet a lot but I didn't found the correct answer.
Thanks
SainathHello sainathn23,
Please close the thread by marking the answers that you got. you can vote for responses, as well, but only the person who open the thread can close it (or moderators)
Ronen Ariely
[Personal Site] [Blog] [Facebook] -
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 -
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.logHi 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 -
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. -
We have replaced a SQL Server 2005 with a SQL Server 2014 (new physical server.) Have the new server set up to use SQL Server login OR Windows user login. Had old server connecting (for a particular DB) to front end Access (2010 or 2013) as guest for
anyone logged into the Windows NT Network with a read only ODBC connection. Have the DB in the new server set to include guest as db_datareader (with only SELECT permission for the securables of each table and view being linked) but when any Windows user not
specifically listed as a SQL DB user tries to use the front end they get an error of:
Microsoft SQL Server Login
Connection failed:
SQL State: '28000'
SQL Server Error: 18456
[Microsoft][OCBC SQL Server Driver][SQL Server] Login failed for user {domain\user}.
After closing that pop-up window a server login window appears. Of course, since the guest user is not specifically listed as a user in the DB that fails also. It seems like there should be a very simple solution to this, but I can't seem to find it. I want
to allow anyone logged in on the Windows system (locally) to be able to open the MS Access file (on their work station machine) and run their own (read only; select) queries on the SQL Server database. Any suggestions?
Thanks a billion in advance ----Thanks for the response Olaf. I have now spent weeks researching this. I realize that using the guest account in most situations is not advised. As mentioned, I have restricted the guest account to allow the db_datareader role only, and have explicitly denied
all other roles, as well as allowing select only, and still have no access for the guest account.
The suggested fix in the second link you provided, of using Windows groups is not plausible for my situation either. We are a scientific field research institution, with a few long term users and lots of users that may have Windows accounts for a few months,
and then they are gone. It would be a nightmare for the network tech to try to keep a group account up to date, and we need to give access (read only, of course) to anyone logged into the system. Realize that the ONLY access of any kind to this database is
thru MS Access ACCDB, using a (by default) read only OCDB connection.
This type of access is used particularly because researchers need to be able to set up their own queries, and the MS Access query interface is particularly convenient for people who are not themselves SQL experts, yet are trying to get some very advanced
levels of output. Putting the database online is not practical because then we are back to the need for a comprehensive query interface, and just picking up general subsets of the data online (from a basic web page search feature) would be out of the question,
since the result set would involve hundreds of thousands if not millions of records.
So - that said - what exactly would you suggest, assuming we don't have the funds to buy a whole new system, and have spent plenty of money with Microsoft's Enterprise level MS Office so that all work stations have MS Access, and Microsoft's SQL Server,
as well as running our network on Microsoft's network software. -
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?
ThanksHi 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.
CharlesIn 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 AdminNot 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] -
How to access Oracle 8g from SQL Server 2005 SP3 EE 64 Bits ?
Dear All,
How to access Oralce 8g from SQL Server 2005 SP3 EE 64 Bits (liked server).
Best regards,
Miguel GavinhosHi!
For the Oracle version is 8.1.6. what should I install, to access Oracle trought a linked server.
Best regards
Miguel Gavinhos -
Accessing v 7 dbase from sql server 2005 enterprise edition
Hi, i would appreciate any help with this issue i have come across when trying to access a version 7 dbase from within sql server 2005.
The error message is telling me that "This version of SQL server man studio can only be used to connect to SQL Server 2000 and SQL servers 2005"
I am new with SQL server so ill explain how im accessing it. I am connecting a server with sql 2005 on it via net support then through this trying to access another server with v 7 on it.
Thanks for the help in advance.I see little purpose in resurrecting or "cleaning out" these threads. I cannot see that asking the OP if the problem still persists after 6 years has any useful purpose - and someone follows along shortly afterwards (since the thread has now risen
to the front of the forum) with a post that he then marks as an answer. It looks like there are over 900 threads in this forum alone that are unanswered - and I'll guess that this forum has significantly less volume than some of the others (9100 in tsql).
If MS wants to apply manpower to that, so be it. But immediately following a "is this still a problem" post with a suggestion/mark as answer does not seem to do much beyond generate volume. At a minimum it is inappropriate for someone
to propose one's own post as an answer regardless of their official forum position.
And if we follow this cleanup logic, what is accomplished if the OP never responds? Odds are that there will be none, so why bother? Alternatively, just actually mark the thread as answered with some sort of "cleanup, no response from OP" post. The
end result is the same.
Well, no one cared enough to answer his question 5 years ago. I want to change that. My time machine is broken right now, but I can still check to see if people still care about their issues. Because I care. Even if it's old. We should all care.
I understand that not everyone sees the value of asking about a 5-year old question. But what exactly does it hurt? How does showing I care about the person become a problem? We made you read it? Is that the problem?
Ed Price, Power BI & SQL Server Customer Program Manager (Blog,
Small Basic,
Wiki Ninjas,
Wiki)
Answer an interesting question?
Create a wiki article about it! -
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.
BillRenaming 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!
Maybe you are looking for
-
Need to email more than 1 file at a time please help
I bought this program so I could email 150 pictures to a Kinkos to be printed this is the only program they could open them up and now I can't figure out how to email more than one at a time is there any way for me to email more than one of these fil
-
In application express under object browser i cant view the list of tables
Hi, In the application Express workspace when i click on Object Browser, we have a list of existing tables which displays. But cant view the table list now. could you please help. I can retrieve the data from the table in the region. I dont know how
-
I can connect my iPhone to my work wifi but when I try to connect my IPad it will not connect. It says safari can not open page. What's up with that I have used IPad connected to work wifi before
-
Want to include ?xml tag and schema when creating XML
My database table that need to be generated in to XML are large and therefore I must use OracleXMLQuery.getXMLSAX . The output is missing the <?xml version="1.0" ?> tag. How do I get it? I am on 9i but have imported the .jar containing oracle/xml/par
-
Email word document as attachment
I have a template in word document with some variables and text in color, bold, grey etc. stored in UNIX directory. My goal is to replace variable with customer name, number dynamically and then send email this word document as an attachment in class