Cant Use ODBC Data Source On SQL SERver 2000 Sp3a Named Instance
Jul 23, 2005
Here's my situation:
I have an ODBC DSN setup for Timberline Data (An accounting package
that uses pervasive.sql) on my sql box. I set up a linked server using
the supplied timberline odbc driver. I have two sql instances setup,
the default instance and a named instance. On the default instance,
the linked server works great no matter who is logged in using it (all
authentication is NT integrated). However on the named instance only
the NT account that the MSSqlserver$NAMED service is logged in under
can utilize the linked server. All others get a ODBC error:
"error 7399: OLE DB Provider 'MSDASQL' reported an error. Access
Denied. OLE DB error trace [OLE/DB Provider 'MSDASQL'
IUnknown::QueryInterface returned 0x80070005: Access Denied.]."
Far as i can tell, both instances are setup the same, except that one
is the default and one is a named instance.
Why the different results for the default instance vs a named instance.
The box I am trying to connect to is running two instances of SQL Server. There is a SQL Server 2005 instance which is the default. There is a SQL Server 2000 instance which is named 'SQLSERVER'. I can connect to the SQL Server 2000 instance no problem:<add key="ConnectionString" value="server=MYPCSQLSERVER;database=mydatabase;user id=****;password=****" /> However, I am having trouble connecting to the Default SQL Server 2005 instance. I have tried: <add key="ConnectionString" value="server=MYPC;database=mydatabase;user id=****;password=****" /> but it doesn't work. I have tried explicitly setting SQL Server 2005 to use port 1434 (as SQL Server 2000 is running on port 1433), and then used: <add key="ConnectionString" value="server=MYPC,1434;database=mydatabase;user id=****;password=****" /> but this doesn't work either.
Am I mssing something here? Any help much appreciated Thanks...
We are trying to quickly put together what needs to be accomplished to install a named instance of SQL Server 2000 on an existing production server (also running SQL Server 2000). It appears as if the install will require a reboot. Can the reboot be postponed until after-hours without impacting the default instance of SQL Server?
Also, I see that if certain services are stopped prior to installing sp4 that you can avoid a reboot. However, if we are unable to stop these services (DTC, for example) without impacting the default instance of SQL Server, will the default instance of SQL Server experience any issues if we postpone the post-sp4 reboot until after hours?
moving to a new sql server box because of a problem with the SAN its connected to. started my named instance in single user mode and restored master. sqlserve.exe -c -m -s ovops now the instance won't start. tried starting it with the -t3608 switch.. won't start!! Its because my drive configuration is different on the new server than it was on the old server, I cannot start the instance because it is expecting model, msdb, temdb and all of the user databases on drives that don't exist?? what can I do?????
I am trying to set up a Named Instance of SQL 2000 on the same machine that has a default instance of SQL 7.0. The setup always completes and I am able to register the Named Instance of the SQL Server with which it was installed on. However, when I try to connect the users to the database, with both windows and SQL authentication, I receive a SQL server not found error. I have tried an alias setup as well as physically specifying the port number in settup up an ODBC connection. Has anyone ran into similar problems? Also, has anyone been able to successfully complete the process as mentioned above?
We have a two node activepassive SQL Server 2000 cluster SP2 running on Window 2000 advanced server SP2. Everything is working fine including failover. Today we migrated over our 7.0 databases to the SQL cluster and they attached fine and upgraded fine but we would like to shutdown the 7.0 server and bring up the clustered SQL Server under the old name. We will be running 3 instances of SQL Server 2000 on the Cluster so at least 2 of these will be named instances like this: "Virtual serverinstance". Is it possible to create an alias for this SQL Server so that we could access the server under the original name of the server??? Thanks!!! Bruce
Hi, I am struggling connection to a named instance of SQL 2000 (SP4) from another machine but without any success. I get an error message saying that the server does not exist or access is denied.
The security configuration in this named instance is the same as the default instance (also 2000) and the remote machine can connect to it successfully.
I also configured the aliases in Client Network Utility in the client machine and set the server (machine) name and the port number used by the instance - but no help.
I use osql and Query Analyzer to connect to it, but I cannot connect by any of them.
Connecting locally, in the machine where the instance is installed, is successful.
The same behaviour appears when I try to connect to another instance on the machine which is 2005. Something with the named instance is problematic.
I've two instances(Default, Named[dynamicsFINANCE]) running on SQL server 2014. However, when I try to connect to named instance say (dynamicsFINANCE) using SQL authentication from local SSMS, I get below error message:
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)
I assigned a static port number to the named instance [dynamicsFINANCE] 1450. I also setup the firewall rule to allow access to Port 1450.
I have a 3 node cluster on which I have installed SSAS as it's own insntance. I have created this as a named instance and can connect to it by serverinstance if I'm on the server itself. However from my desktop I get the error saying instance was not found on server name.
I have defined an alternate port and setup firewall rules and can connect via server:port but not serverinstance. Prior to making this change SSAS was running on default port of 2383 and I could connect just by servername.
I have read many articles for previous versions saying that clustered SSAS will always use 2383 and that you must connect just using servername. However and this is were it gets strange. I have a 2 node UAT cluster with SSAS setup exactly the same way I've described above and I can connect from my desktop as serverinstance.
Should I be able to connect as serverinstances for a named clustered instance in 2012 ?
I am running Microsoft SQL Server 2005 Express Edition, and I am having difficulties setting up an ODBC User Data Source to connect to the SQL server. I have tried going through "Control Panel -> Administrative Tools -> Data Sources (ODBC)" to add a user data source. For the SQL Server to connect to, I have tried specifying "localhostSQLEXPRESS", "SQLEXPRESS", "(local)", etc. -- but nothing seems to work. When the DSN configuration wizard tries to connect to the SQL Server to obtain default settings, it fails with the error "SQL Server does not exist or access denied". (Same error occurs if I try connecting to this ODBC data source later.) But I know that the SQL Server exists and I have been using it through the SQL Server data provider in another application. I am new to this, so any help or pointers would be greatly appreciated. Thanks, Kumar
We have more than 10 databases on the same server. When I try to set up ODBC connection through my desktop to a specific database (DB1) using SQL authentication, it acts weird:
-- I give the login (testkz) access to DB1, DB1 does not show up in the default database list; I tried to type in the database name, it is not taken
-- If I give 'testkz' access to two other databases (and only these two), even though I did not give access to DB1, DB1 together with some other databases show up on the default database list. Seems to me that there are some dependency among the dbs.
I am trying to import tables from an ODBC data source into an SQL Server 2005 database. I presume that one way to achieve this is to create an Integration Services package, via Business Intelligence Studio (I already used DTS in SQL Server 2000, but not Integration Services) ?
Or is there a simpler way ? For instance, is there an import wizard that woult include an ODBC Data source ?
I have a VB 2003 .NET application that I wrote for a customer that connects to a named instance of SQL 2000. Until recently it has been working fine. Lately the program either pops a timeout failure within a few seconds or a general network error. I've increased the connection timeout settings to 90 seconds but the error still pops within a few seconds. I'm thinking something has changed in the environment that prevents a clean connection to the named instance of SQL server.
How should this issue be troubleshoot to determine the problem and what areas need to be looked at?
Hi,I used sp_addlinkedserver to link to a remote server through ODBC.When I execute select count(*) from LinkSrv.SI.DBO.SIHeader in SQL QueryAnalyzer. It returns 13705 records. But when I execute select * fromLinkSrv.SI.DBO.SIHeader. It only return 885 records. If I specify somecolumns, select ODCOMP, ODPONO, ODVDCD from LinkSrv.SI.DBO.SIHeader.It returns more records, 1213 records.I guess there is something limit the return storage, but I can notfind it.Any suggestion will be appreciated. Thank you
Hi, I've downloaded the SP3a for sql server from the microsoft website. I unpackaged the files into a folder and ran the file setup.bat. I recieved an error that setupsql.exe file was not found. I think theres a folder missing called Setup under the X86 folder. Is there a way I can fix this????????
I have set up a new connection as a connection from data source, but I cannot see how to use this connection to create my Data Flow Source. I have tried using an OLE DB connection, but this is painfully slow! The process of loading 10,000 rows takes 14 - 15 minutes. The same process in Access using SQL on a linked table via DSN takes 45 seconds.
Have I missed something in my set up of the OLE DB source / connection? Will a DSN source be faster?
I got this message from Backup Exec for Windows Servers Environment Check 1.0 for SBS1 QUOTE
An instance of Microsoft SQL 2000 was found that is not updated to Service Pack 3a.
An instance of Microsoft SQL Server was found that is not updated to the correct service pack. Using this SQL Server instance with Backup Exec may cause errors. To install Backup Exec successfully, upgrade this SQL Server to Service Pack 3a, or select another instance.
We just upgraded 2 sql servers from sql server 2000 sp3a to sql server 2005 build 2153, and merge rep exists between these 2 servers.
However, after sql server upgrade, we had to reinitialize merge replication and now the merge agent is reporting 2 errors
1)
Error messages:
The Merge Agent failed to upgrade triggers, metadata and stored procedures on the Subscriber to versions compatible with SQL Server 2005. Restart synchronization, and if this failure continues to occur reinitialize the subscription. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199403) Get help: http://help/MSSQL_REPL-2147199403
Invalid column name 'metadata_select_proc'. (Source: MSSQLServer, Error number: 207) Get help: http://help/207
Invalid column name 'delete_proc'. (Source: MSSQLServer, Error number: 207) Get help: http://help/207
The merge process could not connect to the Publisher 'Server:database'. Check to ensure that the server is running. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199368) Get help: http://help/MSSQL_REPL-2147199368
Another merge agent for the subscription(s) is running or the server is working on a previous request by the same agent. (Source: MSSQLServer, Error number: 21036) Get help: http://help/21036
looking inside the sp_MSensure_single_instance stored procedure, it's trying to obtain an exclusive lock on resource 'Merge Agent Name' but fails and returns -1
this is the stored procedure executed by sp_MSensure_single_instance and @retcode = -1 and thus cannot obtain exclusive lock on resource
so i think it's failing because for some reason MSmerge_PAL_role database role does not have enough rights to obtain exclusive lock on necessary resources
i've tried many things to fix this, including scripting out and dropping all merge rep, turning off replication db option and reapplying replication create scripts on the server, and even manually deleting the MSmerge_PAL_role database role but still doesn't work
I am trying to use a DTS package to extract data from an old Pervasive SQL 2000 (Btrieve) data source, and copy into an MS SQL Server table.
I have installed the Pervasive ODBC driver and got linked tables in Access working. I can see the data.
When I create the DTS package, it shows a list of the tables in the drop-down, but when I hit the Preview button I get an unspecified error. I can finish setting up the DTS package, the new MS SQL Sever table gets created, and the field transformations all look correct. However, when I execute the package it fails. In the logs, I get an unspecified error, the only error code I get in log is: 80074005.
Thanks for Microsoft's Windows XP Service Pack 2 and Windows Server 2003 that make the security much stronger. However, besides the invisible benefit so far, I have become the victim of this security policy.
I have several named instances of SQL 7/2000 installed in my machine. They are not visible out of the Microsoft new fire wall. I need to access the instances from outside the fire wall, but I don't know which port I should open for the instances.
From SQL online, the default instance of SQL server is connected through TCP/IP by default port 1433. I could successful open that port and made the default instance visible to outside. However, the port 1433 doesn't work for the named instances. SQL online said, the port for named instance is dynamically (by default) chosen the first time the instance is started. So, actually, I have no way to know the port.
Is there anyway that I can check the database or somewhere to get the port that is used by the named instance?
I have a java compiled jar file, which accept the connection string as follows: -Uusername -Ppassword -Sservername:port
This string works fine with the default instance of SQL Server, I mean as long as you supply the name of the SQL Server as 'SQLServer', but if I want to run it against the named instance of SQL Server like 'SQLSERVERNamedInstance' then the connection is failing, giving me the unknown host error. Any idea why?
We have installed SQL 2000 SP4 on Windows 2000 Server. We created named instances on the SQL server. When trying to connect to named instances from a remote sql client which is on windows 2000 and windows 2003, its throwing an error message saying that remote connections are disabled. But, remote connections are enabled on the SQL server. After changing the component services settings on windows 2003 where sql client is installed, we are able to connect to named instances. But, after applying the same settings on another windows 2003 machine, we are unable to connect to the same instances.
We have another machine where we installed SQL 2005 on windows 2003 SP1. When trying to connect to named instances from any remote client, its throwing an error message saying that remote connections are disabled. But, remote connections are enabled in SQL server settings. We tried connecting to the instances by changing the component services settings but still we are facing the same issues.
Hi, I have a task in hand to migrate (upgrade) from SQL2K named instance to SQL2K5 default instance. There are many intranet applications touching current SQL2K. I would like to perform this upgrade such that I don't have to touch any application code - meaning I don't have to change the connectionstring to point to new Default instance. How can I achieve this?
So, in otherwords, here is what I want to achieve:
Current Server: SQL2K: SERVER_AINSTANCE_A (named instance)
If I have both default, I could achive this by setting up DNS alias after migration done so that any call for SERVER_A would point to SERVER_B. But in my case, I don't have SERVER_A, I have named instance. Is there any solution?
I am trying to perform a distributed query however have a situation I haven't dealt with before the linked server I add to do the query is a named instance (DVD_NASDOMINO). How would I specify this in a query as in the FROM part in a sql statement. I tried the obvious DVD_NASDOMINO.qlsdat.dbo.stmenqry and DVD_NAS.DOMINO.qlsdat.dbo.stmenqry. Both returned errors in the query.
I have a server with sql server 2005 installed as the default instance -- I have a piece of software that needs SQL2000 to be the default instance. Is there a way other than install new sql2005 named instance and move databases to rename my SQL2005 instance from <machinename> to <machinename>sql05 for example?
hi all,I am trying to create a dts package to transfer data from tables in mysql server 2000 database to a db2 UDB v8.1.4 database. When I use ibmdb2 oledb driver for the destination this works fine except that rowsare committed on a row by row basis thus performance is slow. I wantto use the odbc driver but when I define it as the destination, i geterrors saying that the maximum number of rows failed has exceeded theminimum.Does anybody know what to do in order to get the transfer workingusing ibm db2 odbc as the datasource?ThanksLyn
I have opened up a port on a remote SQL instance and can see that the port is LISTENING when using the PortQry tool. I have also set the TCP port in the TCP/IP properties in the IPAll section for that instance, yet I am unable to connect and get an error of
Connection Timeout Expired. The timeout period elapsed while attempting to consume the pre-login handshake acknowledgement. This could be because the pre-login handshake failed or the server was unable to respond back in time. The duration spent while attempting to connect to this server was - [Pre-Login] initialization=1; handshake=14998; (.Net SqlClient Data Provider)
I have done this on other instances, although they were default instances, and it has always worked fine.
We have 3x instances of SQL Server 2012 installed on a single remote server - there's the default MSSQLSERVER instance, then INSTANCE01 and INSTANCE02. I can remotely connect to the default MSSQLSERVER instance through SSMS, but I cannot connect to either of the additional named instances (INSTANCE01 or INSTANCE02).
For example, if I try to connect to "sql.domain.com", I can successfully access the default instance on the remote server. If I try to connect to "sql.domain.comINSTANCE01", I get an error stating
"A network-related or instance-specific error occurred while establishing a connection to SQL Server".
However - if I try to connect to "sql.domain.comINSTANCE01, 49301" (where 49301 is the TCP Port for the TCP/IP Protocol for this SQL Server instance), I am able to successfully connect.
This leads me to think that there's a communication issue with the SQL Server Browser service running on the remote SQL Server and my workstation.
The following items have been verified:
SQL Server Browser is running on the remote SQL ServerWindows Firewall has been disabled on the SQL ServerTCP Ports 1433, 1434, 1954, and 49301 have been opened up on the remote destination's firewallUDP Port 1434 has been opened up on the remote destination's firewall.
