.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Register
 
Win Surprise Gifts!!!
Congratulations!!!


Top 5 Contributors of the Month
Easy Web
Imran Ghani
Post New Web Links

issue with linked server from sql server 2008 to access 2003 database

Posted By:      Posted Date: May 22, 2011    Points: 0   Category :
 

hi,

I am trying to create a linked server from sql server 2008 to a secure access 2003 database(database which has a password), whatever options i am trying the result is i am getting the error 7399("Cannot start your application. The workgroup information file is missing or opened exclusively by another user.".) or error 7303.

I am selecting 'Microsoft.Jet.Oledb.4.0' as the provider. I think the problem is somewhere in

the workgroup files

Please help me in creating this linked server.

 

 




View Complete Post


More Related Resource Links

Linked Server Error 7303 for Access 2003 Database

  
I am having difficulty creating a linked server to and Access 2003 database on my SQL 2005 server.  Whenever I create a linked server through the either the “New Linked Server” tool in the SQL Management Studio or using the sp_addlinkedserver method, receive and error indicating “Cannot initialize the data source object of the OLE DB provider…(Microsoft SQL Server Error: 7303)”.  Although my ultimate goal is to link to a secure Access 2003 database file, the current MDB file I am trying to link to is “unsecured”.  I have already verified that the SQL Service account has read and write access to the folder containing the MDB file as well as the temp directories on the SQL server (suggestions from other forums).  Is there any SQL Server configuration that I need to modify in order to use the Jet 4.0 linked server provider (Microsoft.Jet.OLEDB.4.0)?

Suggestion about exporting data into Access database from sql server 2008 without Linked Server

  

Hello,

    We have a website that was using Sql server 2005. There was a option in Website where when a user clicks a button, Some tables data will be exported to an access database. To achieve this, we have setup a linked server to Access database. We have moved from sql server 2005 to 2008 (64bit). We did not want to use that option of having a linked server now. I am looking for different ways to achieve the task. We also donot want to use OPENROWSET and OPENDATASOURCE .

 

Can someone  give some insight about this?

 

Thanks,

Nag


SQL Server 2008 -- MS Access 2003 Linked server -- Authentication failed

  

I am trying to link SQL Server 2008 - 64 to an MS Access database on a network share. I can get the link to work from the SQL management studio but when I try to do a ODBC query (from another machine)  of a view table pointing to the access db through a linked server using the "Microsoft.ACE.OLEDB.12.0"driver.  The error from the odbc trace is:

"        DIAG [01000] [Microsoft][SQL Server Native Client 10.0][SQL Server]OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "STPRD" returned message "Not a valid account name or password.". (7412) "

Yes the login to the password are good.  I have tried various setting using sp_addlinkedsrvlogin function but nothing will handle the extra hop.


SQL Server 2008 Linked Server SELECT INTO issue

  
I have a SQL Server 2008 installation running on a clustered Windows Server 2008 R2. I am trying to execute a query on a remote SQL Server to create a table. In order to do so, I call a stored procedure on the remote SQL Server. The stored procedure's description is as follows: ------------------------------------- Create procedure [dbo].[USP_RemoteExec] @varSQL varchar(max) as declare @tempSql nvarchar(max); set @tempSql = CONVERT(nvarchar(max),@varSQL); exec sp_executesql @tempSql ------------------------------------- I pass the following command to the remote stored procedure as follows: exec [servername].[dbname].dbo.USP_RemoteExecute @varSQL='if object_id(''testdb.dbo.tmp_testEmpty3'') is not null drop table testdb.dbo.tmp_testEmpty3; create table testdb.dbo.tmp_testempty3(col1 int, col2 varchar(20));' go select * from [servername].testdb.dbo.tmp_testEmpty3 go This statement returns the following: --------------------------------- col1,col2 (0 row(s) affected) But, when I run the following statement: exec [servername].[dbname].dbo.USP_RemoteExecute @varSQL='if object_id(''testdb.dbo.tmp_testEmpty'') is not null drop table testdb.dbo.tmp_testEmpty; select * into testdb.dbo.tmp_testEmpty from (select top 10 mytab.[col1] as [col1] , mytab.[col2] as [col2] , mytab.[col3] as [col3] FROM testdb.dbo.mytab as [mytab] with (nolock)) as A' go select * from [

SQL Server 2008 Linked Server SELECT INTO issue

  
I have a SQL Server 2008 installation running on a clustered Windows Server 2008 R2. I am trying to execute a query on a remote SQL Server to create a table. In order to do so, I call a stored procedure on the remote SQL Server. The stored procedure's description is as follows: ------------------------------------- Create procedure [dbo].[USP_RemoteExec] @varSQL varchar(max) as declare @tempSql nvarchar(max); set @tempSql = CONVERT(nvarchar(max),@varSQL); exec sp_executesql @tempSql ------------------------------------- I pass the following command to the remote stored procedure as follows: exec [servername].[dbname].dbo.USP_RemoteExecute @varSQL='if object_id(''testdb.dbo.tmp_testEmpty3'') is not null drop table testdb.dbo.tmp_testEmpty3; create table testdb.dbo.tmp_testempty3(col1 int, col2 varchar(20));' go select * from [servername].testdb.dbo.tmp_testEmpty3 go This statement returns the following: --------------------------------- col1,col2 (0 row(s) affected) But, when I run the following statement: exec [servername].[dbname].dbo.USP_RemoteExecute @varSQL='if object_id(''testdb.dbo.tmp_testEmpty'') is not null drop table testdb.dbo.tmp_testEmpty; select * into testdb.dbo.tmp_testEmpty from (select top 10 mytab.[col1] as [col1] , mytab.[col2] as [col2] , mytab.[col3] as [col3] FROM testdb.dbo.mytab as [mytab] with (nolock)) as A' go select * from [

Win server 2003+ Sharepoint 2007+SQL Server 2008 ,reports view issue?

  

I hope someone may shed some light on a serious obstacle encountered on a client site:

We have implemented a SharePoint integrated report services solution for the client on a single server

Server = Windows 2003

SQL = 2008

MOSS 2007

Web application = servername:8888 (default) - windows auth

Web application extension 1 servername:8889 (extranet) forms auth

Web application extension 2 servername:8887 (intranet) forms auth

Reports are visible and can be run (renders) on internal sites

However, there is an external site which allows users to access the reports - the issue is, the reports then dont run and I get this:

"An unexpected error occurred while connecting to the report server. Verify that the report server is available and configured for SharePoint integrated mode."

Though I have not actually seen the firewall config of the AAM, the client assures me it has been setup properly.

If the AAM is setup correctly, what could be the problem? The server is clearly available and confgured in SharePoint integrated mode.

 

has anyone experienced the scenario where clients want to publish their reports on an external site? What can one do to see any errors other than the one line message (tried enabling custom errors, but no good)


Upsizing Database from Access 2007 to SQL Server Express 2008

  
I have recently downloaded and installed SQL Server Express 2008 on to my Windows XP SP3 machine, I have a large MS Access 2007 database (.accdb) I wish to export out to SQL Server. I am using the 'upsizing wizard' that is found on the 'Database Tools' tab of Access 2007. Clicking on the 'Database Tools' tab and then on the 'SQL Server' button starts the Upsizing wizard. On the first page of which I select the 'Create new database' option, the next page asks 'What SQL Server would you like to use for this database?' it already has '(local)' entered into the text box, so I leave that unchanged, I tick the trusted connection box and name the new SQL Server database and then click 'Next'. But I get the following error (it appears in a Windows information message box):

Title: Microsoft SQL Server Login
Message Text:
Connection failed:
SQLState: '01000'
SQL Server Error: 2
[Microsft][ODBC SQL Server Driver][Shared Memory]ConnectionOpen(Connect()).
Connection failed:
SQL State: '08001'
SQL Server Error: 17
[Microsft][ODBC SQL Server Driver][Shared Memory]SQL Server does not exist or access denied.

PS. I have successfully used the upsizing wizard to export the same Access database into SQL Server Express 2005 on another machine.

What am I doing wrong this time?

Unable to connect Excel 2003 from linked server in sql 2008 64 bit

  
Hi ALL,

I was unable to connect to excel 2003 with linked server created in sql server 2008 64 bit. This was working fine with sql server 2005 32 bit.

I know that there no 64 bit drivers for JET drivers, but i am looking for some alternative ways to do the same job.

I dont want to migrate to Excel 2007.

Thanks in advance for all your help.

Thanks,
Loknath

Issue when using Distrib.exe to synchronize database with SQL Server 2008 Express

  

Hi

I am using SQL Server 2008 Express. I created a new DB and then used Distrib.exe to create and populate the tables. It worked fine. However then I deleted one of the tables and ran the command again from command prompt. It did not pick up the table that I had dropped.  I did not get any error messages but just a message saying, No replicated transactions are available. I checked the snapshot. The table I dropped is in the Snapshot. I am using a transactional Publication and Pull Subscription.  Any ideas why the the deleted table is being missed by Distrib??

Any help will be much appreciated.

Thanks


Linked Server to Password Protected Access Database

  

I want to create linked server in SQL 2005 with Ms Access 2003 Database. I have used following commands to create linked server.

EXEC sp_addlinkedserver
@server = N'TestLinkServer',
@provider = N'Microsoft.Jet.OLEDB.4.0',
@srvproduct = N'Access',
@datasrc = N'D:\Test.mdb',
@provstr = Null

EXEC master.dbo.sp_addlinkedsrvlogin
@rmtsrvname=N'TestLinkServer',
@useself=N'False',
@locallogin=NULL,
@rmtuser=NULL,
@rmtpassword=NULL

With above command linked server successfully create and can run SQL query against linked server. But if i set Database password to MS Access 2003 Database, then it gives following error message.

The OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server "TestLinkServer" reported an error. Authentication failed.

Any ideas?

Thanks,
Rajesh


Linked server access issue when hosting application in IIS

  

Hi,

I have two instance of database and connected the other with linked server. When i run the application locally its working fine. It gets valur from linked server tables. After hosting the application in IIS im getting following eror.

The OLE DB provider "SQLNCLI" for linked server "LINK" does not contain the table ""90"."dbo"."table"". The table either does not exist or the current user does not have permissions on that table.

 

Can anyone specify what user should be mapped to solve this issue?


Linked server issue on test box, post upgrade 2005 to 2008 R2

  

In an effort to do some testing prior to upgrading our environment to 2008 R2, I made a test instance on our Dev box.  2005 instance, copied as many things as I could think of from various other instances.  Made a basic linked server to our main cluster, had a repeating job to email me results of a query across that link every few hours.

 

Everything was working fine until the upgrade finished.  It completed at ~7pm.  The email at 6PM came through fine (while the upgrade was in progress), the email at 8pm didn't come through.  Checked various things (DB mail was still working, tested fine).  It couldn't access the data across the linked server.  I tried deleting that link and remaking it.  Errors out.  Tried running the same scripts we use to create our standard linked servers, error out.  The only ones that I can set up and function are links to other instances on the same box.

I've looked around at other fixes for this error message and none seem to make any difference.  Log in with Domain cred's, log in with the sa account, no difference.  I can connect from other instances & servers back to this one, just not outbound from this one.  And it worked prior to the upgrade I applied to it.  All other instances on the box are 2005 as well.

Here is the message I ge

Issue with linked server 2008 (and R2) not an issue in 2005

  

Hi,

I have been using SQL 2005 successfully to connect to tables in a 10g Oracle data warehouse. I have been using the 11g client.

I have tried several times to get this working in SQL Server 2008 (and R2) and have tried the 10g and 11g clients...

I do a query like Select top 100 * from DWD..DW.IC_TRAN_PND and I get the error: 

"Invalid data for type "numeric".

 

I have read about the reasons for this but is there a way to make it work like it does in SQL server 2005?


2008 server Access database connecting win7 workstation with ODBC link works extremely slowly

  

I have an Access database on a 2008 server (64 bit), and notebooks with 32 bit win7. The program using the mdb is written in delphy, and running on my notebook, and working on data extremely slow. What can be the problem?

The database connector is an ODBC linked network drive.

On that same configured PC with XP it works normally.

Pappxla


Trying to add a linked server - SQL Server 2008 Express Edition to Access 2007

  
OS: Vista SP1
SQL Server 2008 Express Edition installed locally
Office 2007 installed locally

I'm trying to add a linked server to a named instance of the SQL Server 2008 that links to an Access 2007 database.

I've spent a couple of hours trying this now - many, many different ways.

Always seem to end up back at Error 7303 - http://msdn.microsoft.com/en-us/library/aa226395(SQL.80).aspx

I've tried all versions of Access database file 2000, 2002-2003, 2007
I've tried to use different drivers -

Microsoft.Jet.OLEDB.4.0
ODBC
Office 12 for Access driver

I've tried to use the upsizing wizard from Access - no good, cannot get it to connect to the SQL Server 2008 Express Edition instance

Whichever way I try it I end up with this message/error:

the upsizing wizard only works with microsoft sql server versions 6.50 sp5 or higher

I've read: http://support.microsoft.com/default.aspx/kb/838594 and followed it - same error.

I really want this to just work. Like it should already.

Any suggestions appreciated.

Matt Haddon

Are linked servers an issue on SQL Server 2008 R2 64 bit platform?

  
Recently a Microsoft employee strongly recommended not using linked servers at all.   I have a different thread on this topic which died.  However, I'd like to get feedback regarding linked servers on SQL Server 2008 R2 64 bit platforms.
michelle jenks

Linked Server From SQL 2008 R2 (32 or 64 bit) TO Access 2007 mdb

  

I have what I thought was a simple task.  Create an OLEDB connection to an Access2007 MDB data file within SQL Server 2008 R2.  Here's my environment:

    Windows 7 64-bit OS
    SQL Server 2008 R2 Standard 64-bit
    Office 2010 32-bit (installed 32-bit because all legacy data needed to be ported)

My first attempt was within SQL Server's Management Studio by navigating to Server Objects - Linked Servers and right-click selecting New Linked Server...
First indication of some trouble began when I didn't see an ODBC Provider for my Access database.  After trying a few options, I turned to Google expecting a quick resolution.  Here is the beginning of 5 days of going round in circles!!!

Eventually I found some links that led me to potential solutions:
http://social.msdn.microsoft.com/Forums/en/sqlgetstarted/thread/589ca193-3541-4c5e-965c-4c515d6b476b
http://social.msdn.microsoft.com/Forums/en/sqldataaccess/thread/c371fb35-6bdd-42e6-b88e-d1c0003d23f6
http://social.msdn.microso

Categories: 
ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend