I am running SQL Server 2000 sp4 in Win Server 2003. I have a DTS
packages which connects to FileMaker 6 files via the ODBC driver
installed with FielMaker.
The DTS packages work correctly when
executed directly. However, when executed from a SQL Server Agent job,
the same DTS packages fail. Always with the same message:
Error: -2147467259 (80004005);
Provider Error: 16394 (400A)
Error string: [FileMaker][ODBC FileMaker Pro driver][FileMaker Pro]Connect failed
Error source: Microsoft OLE DB Provider for ODBC Drivers
Searching
for info on the above message seems to indicate a permissions problem.
However, I am running the jobs with an full administrator account. All
connections and the FielMaker files reside on the one server.
Win 2003 Small business server with IIS being used as a web server. Our client app can log in and run queries, but our web app when trying to log in gets the message, 'SQL server does not exsist or access denied' The system DSN's are both sql drivers and the configuration is name pipes. Our recomended specs use TCP/IP, but when I try to change it, it craps out on me. He's opened up his firewall completely to this new box and his old box, a Win2k machine can connect using TCP/IP. This machine is in a work group. Any suggestions on what it might be??? :confused:
i have an sql express db on my webserver. now from another computer I am trying to creat an odbc connection to the sql server but when I enter in just the ip and the login and password it fails. Please advise me what I can do?
what i really am trying to do is set up an access db on my home computer to be linked to an sql server express backend. I thought to do this with odbc - is this the correct way?
I'm a new comer to this APS language and hope sombody out there can help me with this I'm trying to find codes for me to connect from ASP to Sql Server using ODBC. Can anyone help me Thanx
Could someone tell me how to use a query with a "connection string" to connect to an ODBC driver and retrieve data from its tables. I am new at this and have been having a lot of trouble connecting from the SSIS manager. If someone has a tutorial on how to do this. I would really appreciate it.
Hi all I have problem with making Connection between two computer through SQLServer and ODBC.
I have two computers which are members of a WorkGroup network with WindowsXP(sp2) installed. on one computer i have installed SQL Server 2000 Enterprise edition with MIX Authentication mode enabled. Also i have created a LOGIN (Sql Server Authentication) with System Administrator ROLE (SYSADMIN).in that sql server environment .
But in another computer when i want to create an ODBC connection (ControlPanelAdministrative ToolsData Sources (ODBC)) to connect to mentioned Computer with Sql server,I receive the following Error: Access Denied...Sql Server doesn't exist.
I have disabled Windows-XP firewall on both computers but still problem persists. By the way these two computer have one Administrator Account with DEFFERENT Passwords.
Could anyone help me.? Any help greately would be appreciated.
Installed SQL2005, connect via (the new) SQL Nativ Client ODBC Vers. 2005.90.1399.00 works, just as (the old) SQL Server ODBC-Driver 2000.85.1117.00. Works fine.
I create a Test database in SQL server, also I add new user in security folder. Also I add this user in Test database, the permission are: Public, and db_owner. But when I let the user try to open the database, it is ODBC – Connection failed. I add another user a few months ago, she works fine. But the new user I added in didn’t work, did you know why. I am sure I add the same permission as the later user. Thanks.
Please excuse my lack of poper terminology when describing my issue to you, as I am very new to databases.
I have set up a SQL Server database which connects via MS Access. The application works fine, except when trying to connect through VPN.
Through System DSN, I changed the server name (FSERVER) to the server IP address, and test completed successfully. I am also able to ping the server when connected via VPN. However, when I try to start the application, I receive the following error after several seconds:
ODBC-- call failed.
That's it. No other information about the error. I read somewhere to make sure the MDAC versions are the same, which they are.
As I say, I am quite new to this, but would really appreciate any guidance to help me through.
Running a database using sql server. User, rights, password set up on the server side and is functioning fine on the users normal desktop. But here is the problem. When the user goes to a different desktop they have never been on before and a new user profile is created on that desktop, they are unable to access the database. When using the front end (access), an odbc connection failure popup occurs when trying to retrieve data. The wierd part is that the odbc connection was set up under admin tools just like it is setup on the working desktop. Also the connection tests successfully. This leads me to believe that it is a desktop side problem and not server side. It is only a problem when a new user profile is setup on a desktop that the user has never been on before.
I have installed SQL2014 on a server [hostname: sql2014]. Â I created an user "ABC" and even granted "system admin" server role. Â I tested login from the Management Studio in the local server and succeeded.Now I would like to create an ODBC connection from a IIS server to this SQL2014. When I tried create the system DSN with the user "ABC" by selecting the "With SQL Server authentication using a login ID and password entered by the user". Â It gave me the following error: Connection Failed:
SQLState: '28000' SQL Server Error: 18456 [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'ABC'.
From the sql server log file viewer, I found an event with the following:
Login failed for user 'ABC'. Reason: Could not find a login matching the name provided. [Client: 192.168.0.1]I can create the ODBC connection with the option "With Windows NT authentication using the network login ID". Â But for security reason, I need to use SQL server authentication.Here are some more information.Both SQL and IIS servers are running Windows 2012 DataCenter.I am using Mix mode authentication for the SQL server.I turned off firewall on both servers.I can ping each other successfully.I tried install the SQL server native client for SQL2012, but the error is just the same.
I have a problem which I can't seem to understand what is the cause. Please help!!!
I have this access which run under oracle 10g. Here is the code (below) that I always get error in. When I got into this error, I go to Control Panel -> Administrative Tools-> Data Sources (ODBC) then I choose on acc (microsoft Access Driver (*.mdb)) and click Configure. I select the access and click repair. It get through and I thought that I solve the error, but every time that I close and open the access when try to run, I receive the same error again. If I goes to the same process, click repair. It work, but I have to do it every time that I close and re-open the access. Does anyone know how to make it default so that I don't have to go the same process every time. Thank you.
I am trying out a simple ASP.NET application which includes access to an SQL Server Database. It works fine on my local machine when I connect to the SQL Server and use SQL commands (via C#) to access it. But my web hosting provider uses ODBC drivers for database access (they support the SQL database type). I would like to find out how I should connect to my SQL Server database and program the access in order for it to be ODBC compatible, so that I can deploy it to my web hosting server. I should also mention that I am using Visual Web Developer 2005 Express Edition. Thanks for any help or pointers. Kumar
Hi all, I'm not a db guru and probably this is a very simple question for you, but I was wondering if it was possible to connect to a SqlServer using odbc without DSN. I mean, I'm trying to connect to the db server from a linux (Fedora Core 8) workstation, using odbc drivers, but it looks like I can do that only using a DSN connection and setting properly the odbc.ini file. It doesn't work, if I use a connection like this from a PHP script: $cn = odbc_connect("Driver={SQL Server};Server=MyServer;Database=MyDatabase", "MyUser","MyPassword") Does anyone know how to connect to SqlServer with a DSN-less connection? Could you explain me where is the error?
I'm using SQLServer2005, Fedora Core 8 with the last FreeTDS installed.
I wanted to know if there is a way to connect to my MSSQL without having to setup a datasource in the control panel.
Perferably I want to locate the database within my perl code instead. I don't want to have to setup a datasource each time I need a different database. Perhaps there is a way to pass the name of the database along with the username and password through the command line.
I am trying to connect to a database and run a query using vbscript. The problem I have run into currently is that I can not get the connection to open even though I know the DSN name it still says it can not find it. I am fairly new to vbscript so I am not sure exactly what it is looking for in the connection string so that it will find the database. Any ideas?
I've been running some tests with a 3rd party application during the last few days, but the ODBC doesn´t seem to be working well.
The ODBCs are configured to go through specific ports, since there's a firewall between the server (production area) and the database (which is located in the dev area). If i press the TEST CONFIGURATION button after i configured the ODBCs, the test is successful, and the log file of the firewall monitor shows that the server is connecting through the designated ports.
But when i run the 3rd party application, the queries fail, showing an error that says "The server cannot be found or you don´t have access", after this error, another one appears, saying something like "Connection().opened..." - unfortunately I don't have the actual text, I'll try to post it as soon as i get them .
Just to make sure that the 3rd party app is doing its job, dev team wrote a simple VB6 app to query the database, and it shows the same error.
Both apps are running well in the dev environment, since dev machines don't have to go through the firewall, and both apps are using the ODBC configured in the same way as the server. I could think that the problem is the firewall, but the firewall logs show that the production server is trying to use ports 1433, 1434, 445 and 139, and there isn´t a single entry showing activity for the ports specified on the ODBCs configuration.
The database server is running SQL Server 2000, the dev pcs are running Windows 2000, and the ODBC driver version is 2000.85.1117.00.
On the Production environment the server that is trying to access the database is running Windows 2003 Server Ent Ed. SP 1 , and the ODBC driver version is 2000.86.1830.00
I hope some one outthere has any ideas to solve this problem, or at least any idea of what is causing this error, because i´m running out of them.
We are using an Access 2002 front-end with SQL Server 2000 as the database.
There is a table (dbo_PrivateGroup) that if you try to open it in the table view, in a query, in a report, or through the application, you get the following Error message:
ODBC--connection to 'unlocking' failed.
Does anyone know what this means and how I am supposed to get around this?
I tried it on the actual server itself and I can read the table through Access, through the application when it is running, and through Enterprise Manager. This machine is logged in with "Administrator" as the user id.
The table is on a different database than the other tables in the application.
It is a user table. And I checked the permissions and all users have select, insert, and delete permissions allowed. However, when I go to look at the columns property, none are checked for any user and when I go to check the boxes for all columns, I hit Apply, then Close. When I go back into that screen for that given user, the columns weren't saved.
My database knowledge is creating tables, stored procedures, and triggers. They don't have a DBA here and my knowledge is limited. Is the problem in SQL Server or Access?
I don't know if any of this makes sense. But if it does, any help would be greatly appreciated.
Hi!It has been weeks now that I have been trying to fix an error that Iencounter everytime it gets to the code at runtime:SQLStmt = "SELECT Sum([Quantity in Stock]) As TotalInStock,Sum([Cost] * [Quantity in Stock]) AS TotalCost " & _"FROM [Inventory Products] WHERE [ItemNumber] = '" & ItemNum & "'"Set InvP = CurDB.OpenRecordset(SQLStmt, DB_OPEN_DYNASET) '==>it gets the error hereI tried also to implement the same code using ADODB but still go the sameerror: "ODBC--call failed".There are other events where similar code is executed without any problemsat all.Any guidance would be helpful.Thanks
I moved a sql 2000 database to a sql 2005 server. I have a front end in access 2003. I manually created an ODBC data source system DSN using the ODBC Data Source Administrator just like it was on the other server. I can connect fine but users are saying their getting an odbc call fail. I created the connection and relinked the tables to the new server with the moved database. I completed the same task with another database and the user can connect fine. What could be the problem?
I want to create an ODBC connection using windows authentication but it always failed. The error display that the database server not found. Is the any configuration I should set before create the ODBC ? Thanks in advance.
We have this fairly simple Access database with a link table to a view in an SQL Server. The Select Query in Access is a simple select from this view with a view criteria set. Nothing fancy. What is driving is moderately crazy is that this Select Query in Access seems to work fine for months and than all of a sudden (same query performed around the same time with about the same workload on the SQL-Server) it responses with the helpful "ODBC-Call Failed" message. Closing the Access database, taking a coffee, coming back againg and try the exact same Select Query normally works, no "ODBC-Call Failed" message.
It not happens always, mosty we're fine. When it happens it happens for all subsequent queries tried. We have to close and reopen the Access database and pray to the good Lord that it works.
We would be very interested in someone with a solution to this problem.
I have a problem when I tried to create an ODBC to SQL Express from Windows 98. Is there any component that I have to install first ? Thanks in advance.
I am having an issue that i can't seem to resolve. By no means am I an expert with odbc connections and what not but any help would be great.
here is my issue. I have a 64 Bit terminal server that is running MS Access. I have defined my DSN within the 32 bit admin utility and it connects without a problem As soon as i try to link tables and make a connection to the database from within Access i recieve an "ODBC CALL FAILED" message.
I enabled tracing and here is what i got.....this doesn't mean anything to me but hopefully it does to someone.....
PaintJobShip_Ma 1388-ecc ENTER SQLAllocEnv HENV * 002DB3C4
When I begin Enterprise Manager and open a connection to a Server, it fails with a timeout error. But if I do a refresh and then connect again, it immediately works. I have had similar symptoms setting up a data source for ODBC. When you initially logon to SQL Server to define the connection it times out. But then if you immediately try again it succeeds. Furthermore one of my application programs fails to work (due to the timeout) on systems that have this behavior. I have had these symptoms occur on 2 diferent workstations, but other workstations access the SQL Server with no problem. All systems are WinNT 4.0; the engine is SQL Server 7 with SP2. The timeout is defined as 15 seconds so should be long enough.
Does anyone know what is going on, or how to fix it?
I am running SQL 2005 SP1 on Win 2003 Std x64 SP2. I get an error trying to connect using an ODBC System DSN connection. The ODBC connection gets the following error:
Connection failed: SQLState:'28000' SQL Server Error: 18456 [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'sa'
The SQL Server logs the following error:
18456, Severity: 14, State: 8.
I have tried this with several SQL accounts. I am able to login to the SQL Manager with the accounts without issue. It is only when trying to connect via ODBC that I get the error. I am currently downloading SQL 2005 SP2 to see if this will help with the issue. Any other ideas would be greatly appreciated.
Using the above connection strings in SSIS design mode, the datasource test succeeds, and an sql select statement in a datasource reader returns the table structure with no error.
However, when I try to run the package, I receive the following error.
SSIS package "Sales Data Load.dtsx" starting. Information: 0x4004300A at Data Flow Task, DTS.Pipeline: Validation phase is beginning. Error: 0xC0047062 at Data Flow Task, DataReader Source 2 [408]: System.Data.Odbc.OdbcException: ERROR [IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified at Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSConnectionManager90.AcquireConnection(Object pTransaction) at Microsoft.SqlServer.Dts.Pipeline.DataReaderSourceAdapter.AcquireConnections(Object transaction) at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostAcquireConnections(IDTSManagedComponentWrapper90 wrapper, Object transaction) Error: 0xC0047017 at Data Flow Task, DTS.Pipeline: component "DataReader Source 2" (408) failed validation and returned error code 0x80131937. Error: 0xC004700C at Data Flow Task, DTS.Pipeline: One or more component failed validation. Error: 0xC0024107 at Data Flow Task: There were errors during task validation. SSIS package "Sales Data Load.dtsx" finished: Failure.
Furthermore, I have packages configured in SQL 2000 DTS to use the same system dsn without any errors.
Database server: - Remote machine running SQL 2005 Standard as a named instance - Named pipes and TCP are enabled for remote connections - SQLBrowser service is running - Listening on default named pipe (\servernamepipeMSSQL$instancenamesqlquery)
Client: - Vista Business machine - Not in same domain as server, but on the same network (via Cisco VPN) - SQL 2005 Express is installed (for use with local databases) - Windows Firewall enabled - Running Symantec Antivirus, Corporate Edition
Connectivity: - I CAN connect to SQL 2005 databases on the remote server using "nperverinstancename" - I CAN connect to SQL 2005 databases on the remote server using Excel 2007
The problem is that I cannot successfully create an ODBC datasource using the "ODBC Data Source Administrator" application. I'm using the "SQL Server" driver and trying to create a System DSN. I'm also running the tool with elevated permissions.
- When I try to use "servernameinstancename" as the server and TCP as the connection type, I get this error:
Connection failed: SQL Server Error: 18452; "[Microsoft][ODBC SQL Server Driver][SQL Server] Login failed for user ''. The user is not associated with a trusted SQL Server connection.
- When I try to use "npervernameinstancename" as the server and Named Pipes, I get this error:
Connection failed: SQLState: '01000'; SQL Server Error: 1326; [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen(Connect()). Connection failed: SQLState: '08000'; SQL Server Error: 17; [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied.
Help! I've really been beating my head against the wall on this one. It all works just fine with a Windows XP client machine.
Using the above connection strings in SSIS design mode, the datasource test succeeds, and an sql select statement in a datasource reader returns the table structure with no error.
However, when I try to run the package, I receive the following error.
SSIS package "Sales Data Load.dtsx" starting. Information: 0x4004300A at Data Flow Task, DTS.Pipeline: Validation phase is beginning. Error: 0xC0047062 at Data Flow Task, DataReader Source 2 [408]: System.Data.Odbc.OdbcException: ERROR [IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified at Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSConnectionManager90.AcquireConnection(Object pTransaction) at Microsoft.SqlServer.Dts.Pipeline.DataReaderSourceAdapter.AcquireConnections(Object transaction) at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostAcquireConnections(IDTSManagedComponentWrapper90 wrapper, Object transaction) Error: 0xC0047017 at Data Flow Task, DTS.Pipeline: component "DataReader Source 2" (408) failed validation and returned error code 0x80131937. Error: 0xC004700C at Data Flow Task, DTS.Pipeline: One or more component failed validation. Error: 0xC0024107 at Data Flow Task: There were errors during task validation. SSIS package "Sales Data Load.dtsx" finished: Failure.
Furthermore, I have packages configured in SQL 2000 DTS to use the same system dsn without any errors.
I am using Windows XP SP2 with a Sql server 2005 Express installation. I created a test db with a user called test, schema also test. I gave the permission connect, db_datareader and db_datawriter. I can now connect into this user using WinSQL. But if I want to connect using a application which is using ODBC, then I get the error:
[SQLSTATE=28000 - [Microsoft][SQL Native][SQL Server]Login failed for user 'test'.[Native Error=18456]]
Because I connect using ODBC, I think there must be the problem. But I have to connect with ODBC. There is no other possibility.
any ideas ?
Regards, Waff
I found this out:
The server collation is defined to: Latin1_General_CI_AS
If I create a new login id in lowercase, then ODBC will change it to uppercase and then the server refuse the access. But why. CI means case insensitive, so doesn't matter if upper or lower case. should.
How do you use a id in lowercase and connecto via ODBC ?
I have a database with primary and Unique key contraints on SQL Server 2000. I'm front ending it with Access 2k.
I want to trap the error when the Unique key constraint is hit, but i can't capture the error number. All attempts return error 0.
The error i get is [Microsoft][ODBC SQL Server Driver][SQL Server]Violation of UNIQUE KEY constraint 'IX_lut_Referral_Source'. Cannot insert duplicate key in object 'lut_Referral_Source'. (#2627)[Microsoft][ODBC SQL Server Driver][SQL Server]The statement has been terminated. (#3621)
I've tried the soultion given here http://support.microsoft.com/kb/q185384 but now get a Type mismatch error on errStored
SaveRecODBCErr: ' The function failed because of an ODBC error. ' Below are a list of some of the known error numbers. ' If you are not receiving an error in this list, ' add that error to the Select Case statement. For Each errStored In DBEngine.Errors
