Transferring MS Access Tables To SQL Server 2005: PRODUCT LEVEL TOO LOW Error
Jun 27, 2007
Hi,
I am using MS Access 2003 SP2 to maintain some data tables. I use SSIS to transfer them to SQL Server 2005, Enterprise Edition.
When I run the SSIS package from within Visual Studio 2005, the package runs without error.
When I try to run the same SSIS package by double-clicking on it in my File System (which invokes the Execute Package Utility, Version: 1.0) none of the tables get copied. Instead all I receive is a message for each table,
Error: SSIS Error Code DTS_E_PRODUCTLEVELTOLOW. The product level is insufficient for component "Data Conversion 1" (49).
The only data conversion I perform is double-byte characters to single-byte characters.
Bob Bojanic, MSFT, made a few suggestions about this in another thread -- but I have created this new thread to help focus on this specific issue. In particular, he asked if we have installed the complete SSIS support for SQL Server 2005, Enterprise Edition, and my network support and database support staff assure me that such complete SSIS support was installed.
Are others having this problem?
Dan
(I just took a look at some of the transformations in the Data Conversion task, and many of them are using an Output Alias identical to the Input Column name. Might that be causing the problem? I will try changing the Output Alias for some tables and see if they then transfer correctly. The "identical name" Output Alias values were created by the Migration Wizard for a DTS 2000 package.)
View 10 Replies
ADVERTISEMENT
Jun 30, 2007
Configuration: Windows XP Pro with SQL 2005 Workgroup Sp2
Hi, we have a package that runs fine in BI Studio but fails with the following error when executing it using DTExec.
Code: 0xC00470FE
Source: Data Flow Task DTS.Pipeline
Description: SSIS Error Code DTS_E_PRODUCTLEVELTOLOW. The product level is insufficient for component "Derived Column" (10660).
The package imports a CSV into a table mapping some columns. The MSDN article at http://msdn2.microsoft.com/en-us/library/ms143761.aspx describes features supported by different versions.
The article says OLE DB source/destination adapters are supported in WG edition but a couple of lines later seems to imply that all source/destination adapters are not supported in WG.
Could you clarify whether stuff like import of a csv into a table with some column mappings should work in WG edition? Also if we have a legacy SQL 2K package doing the same thing, will that work in WG edition? Thx.
Features/Integration Services Enhancements
EE (32-bit) DE (32-bit) EE (64-bit) DE (64-bit)
SE (32-bit)
WG (32-bit)
SSE (32-bit) SSEA (32-bit)
SE (64-bit)
SQL Server Import and Export Wizard and supporting connections, source and destination adapters, and tasks
Yes
Yes
Yes
No
Yes
Execute SQL Task
Yes
Yes
Yes
No
Yes
OLE DB Source and Destination Adapters
Yes
Yes
Yes
No
Yes
SSIS command prompt tools
Yes
Yes
Yes
No
Yes
SSIS Package Designer
Yes
Yes
Yes
No
Yes
Legacy support for DTS packages
Yes
Yes
Yes
Yes
Yes
SSIS Service
Yes
Yes
No
No
Yes
All other source and destination adapters, tasks, and transformations, except for those listed below
Yes
Yes
No
No
Yes
View 3 Replies
View Related
Jul 23, 2007
This thing is driving me crazy. I have a simple flat .txt file I'm trying to import into a DB, and this USED to work perfectly with SQL Server 2000. With 2005, I get "product level insufficient."
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=217596
I've read that and I've looked around. It seems like the solution is to actually connect to the Windows box that the server itself is running on (where SSIS is installed) and import there?? But that's a pain.. that means I'd have to Remote Desktop into the server EVERY time I want to import a text file. Surely there's some other way to do this??
Any advice would be great. Thanks!
View 4 Replies
View Related
Feb 2, 2008
How do i see what SSIS i have?
Threads seem to point that SSIS needs to be installed to fix the following error:
Operation stopped...
- Initializing Data Flow Task (Success)
- Initializing Connections (Success)
- Setting SQL Command (Success)
- Setting Source Connection (Success)
- Setting Destination Connection (Success)
- Validating (Error)
Messages
Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Destination - DataID" (34).
(SQL Server Import and Export Wizard)
Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Data Conversion 1" (55).
(SQL Server Import and Export Wizard)
- Prepare for Execute (Stopped)
- Pre-execute (Stopped)
- Executing (Success)
- Copying to `DataID` (Stopped)
- Post-execute (Stopped)
- Cleanup (Stopped)
But when i choose Help-> About
i get
Microsoft SQL Server Management Studio 9.00.1399.00
Microsoft Analysis Services Client Tools 2005.090.1399.00
Microsoft Data Access Components (MDAC) 2000.085.1117.00 (xpsp_sp2_rtm.040803-2158)
Microsoft MSXML 2.6 3.0 4.0 5.0 6.0
Microsoft Internet Explorer 7.0.5730.11
Microsoft .NET Framework 2.0.50727.832
Operating System 5.1.2600
Where is SSIS info?
View 3 Replies
View Related
Oct 10, 2006
Hi,
I have a SSIS package which I had created on my machine, running Windows XP with SQL2K5 Development Edition. If I run the package through the BI studio or by clicking the dtsx file, it runs without any issues.
When the same package is deployed onto another machine (SBS 2003 with SQL2K5 Workgroup Edition), the package errors with the above message when the dtsx file is clicked and run. However, if the source files are opened up and ran from within the BI studio, it all runs OK.
I've ran through the SQL setup file (through Add/Remove Programs) and Integration Services is installed, however the SSIS service is not on the machine. I've read however that the service is not required to run the package, so what gives? Plus, this doesn't explain why running it through BI studio is fine but not when run by itself.
The data flow task that the package fails on contains 2 SQL sources, 1 SQL destination, 3 sorts, 1 multicast and a couple of merge joins. Are some of these pieces not available in the Workgroup Edition? This would still not explain why it can run in the BI studio on that machine...
Any information provided would be great.
Regards
Alex
View 1 Replies
View Related
Jun 15, 2007
Hi!
I just used the SSIS Import and Export Wizard to copy 50+ tables from SS05 to SS2K.
I found that the wizard created a package that I could not figure out how to edit, e.g., to change whether or not it had to CREATE a table, or just use an existing one. (I created some problems by manually editing the receiving table names to be ones that already existed -- but the original names it had did not exist, so it knew it had to create them. What I should have done, and eventually ended up doing, was scroll through my list of tables in the "receiving" box; I just figured editing the name would be faster, not realizing what problems I would create for myself.)
Anyhow, now that I see the complex package that the wizard creates, with a LOOP over the 50+ tables, I would like to know how/where in the package it is storing the information about the tables to copy.
Basically the wizard creates the following Control Flow tab entries (in processing sequence order):
an Execute SQL Task: NonTransactableSql
an Execute SQL Task: START TRANSACTION
a Sequence Container: Transaction Scoping Sequence, which contains
an Execute SQL Task: AllowedToFailPrologueSql
an Execute SQL Task: PrologueSql
a Foreach Loop Container, which contains
a Transfer Task with an icon I did not notice in the Toolbox
an Execute Package Task: Execute Inner Package
an Execute SQL Task: EpilogueSql
an "on success" arrow to
an Execute SQL Task: COMMIT TRANSACTION
an Execute SQL Task: PostTransaction Sql
an "on failure" arrow to
an Execute SQL Task: ROLLBACK TRANSACTION
an Execute SQL Task: CompensatingSql
Where, and how, can I look within this package to see the details about the tables I am transferring? I see that one of the Connection Managers is "TableSchema.XML" -- but it points to a temporary file on my hard drive, that I presume is populated by the package. Where does it get its information?
This is certainly much more complex than the package I would have written, based on my limited knowledge of SSIS. I would have been inclined to create 50+ Data Flow tasks, one for each table.
So now I'm trying to understand why the Wizard created this more-complex package.
Any help will be appreciated, including references to non-Microsoft books/websites/etc.
Thanks in advance.
Dan
View 17 Replies
View Related
Jul 28, 2006
While executing SSIS package from command prompt as follows:
dtexec.exe /DTS "MSDBetl-hyundai-package" /SERVER tvmwindev02 /CONNECTION "TVMWINDEV02.HISNA_POC";"Data Source=TVMWINDEV02;In
itial Catalog=HISNA_POC;Provider=SQLOLEDB.1;Integrated Security=SSPI;Auto Translate=False;" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING E /CONSOLELOGO
while executing the package following error message is received as :
Error: 2006-07-28 15:12:36.60
Code: 0xC00470FE
Source: Data Flow Task DTS.Pipeline
Description: The product level is insufficient for component "Data Conversion" (202).
End Error
and at the end as :
DTExec: The package execution returned DTSER_FAILURE (1).
Same error appers while executed from Integration Services - ->stored packages - - >name of the package -> mouse right button, run package.
But the same executes perfectly from visual studio, where it is developed.
what could be the reason?
View 6 Replies
View Related
Mar 16, 2006
Running eval. edition of Sql Server Standard 2005. "Insufficient product level" error is thrown during validation phase of an OleDBCommand data flow task. This task type is not licensed in Sql Server 2005 standard? The component runs a very simple sql update statement against a one row table in Sql Server 2005.
If it works from BIDS, should it not work from dtexec.exe on the same box?
Does dtexec run under the security context of the logged in user?
Thanks,
Ken
View 6 Replies
View Related
Jun 5, 2007
Hi all, while executing my ssis package Im getting this error
" the product level is insufficient for component "data reader source" "
but through the bussiness intelligence while debugging it was executing successfully,
but only after deploying the package on to the IS server, while executing getting this error
I checked with the server version also, its was with service pack 2
can I get any help
thanks in advance
View 1 Replies
View Related
Nov 23, 2006
Can anyone give me some ideas on how can i transfer data from access database to sql 2005. It is bit complicated any help will be highly appreciated.
View 1 Replies
View Related
Jan 28, 2008
I am trying to get SQL Express 2005 installed, I have tried this on two PC's within the Domain. Both get the same error. I am the Admin, MCSE since 1999, but I DO NOT know much about SQL. Have search Google for two days, renamed DLL's, installed localy, copied off the CD, update .net, windows updates.... The PC will load SQL 2005 (full version) and 2000, but the app doesnt seem to want anything but the Express version... any ideas would help...
btd43@hotmail.com westcoastpc@gmail.com
Product: Microsoft SQL Server 2005 Express Edition -- Error 1937. An error occurred during the installation of assembly 'Microsoft.SqlServer.Rmo,Version="9.0.242.0",Culture="neutral",processorArchitecture="MSIL",PublicKeyToken="89845dcd8080cc91",FileVersion="9.0.2047.0"'. The signature or catalog could not be verified or is not valid. HRESULT: 0x80131045. assembly interface: IAssemblyCacheItem, function: Commit, component: {D1B86CEE-1C5E-4960-B99F-7142D1582B1B}
View 1 Replies
View Related
Aug 22, 2007
Hi,
While I am trying to install SQL server 2005 I get the following message - "Machine does not have a product that matches the installation package". The installation does not occur.
I am using Windows 2000 Professional SP4 and using 32 bit installer - SQLServer2005SP2-KB921896-x86-ENU.exe
Help would be appreciated... thanks.
Regards,
Ravindranath Kini
View 6 Replies
View Related
Feb 26, 2007
I am receiving the following error when I try to execute an SSIS package that is saved to a structured file. I am using DTExec to execute the package.
Description: The task "Initialize Variables" cannot run on this edition of Integration Services. It requires a higher level edition.
After some research, I was able to find a supporting article in SQL Server 2005 BOL at http://msdn2.microsoft.com/en-us/library/aa337371.aspx
The issue was resolved by installing the Enterprise Edition of SQL Server Integration Services (Windows Service) on the local server (server where the package is saved and executed from). However, this goes against my original anticipation that the SSIS Windows Service would only need to be installed on a machine where I needed to store packages and/or monitor package execution. Not if I wanted to execute packages.
Unfortunately, my package is using advanced options (as identified in the BOL article previously referenced).
Am I missing something??
Sincerely,
Sean Fitzgerald
View 3 Replies
View Related
Mar 13, 2006
I am trying to run dtexec on some DTSC packages I created using SSIS. I keep getting the error "The product level is insufficient for the component". Anybody know what this means?
Thanks,
Michael D. Fox
View 4 Replies
View Related
Oct 22, 2007
Hi,
I have created a package where Iam transferring data from oracle to sql 2005 server and I am getting below error message.
[OLE DB Source [1]] Error: An OLE DB error has occurred. Error code: 0x80040E10. An OLE DB record is available. Source: "Microsoft OLE DB Provider for Oracle" Hresult: 0x80040E10 Description: "ORA-01008: not all variables bound ".
The query which I got from oracle team has the following note
---- NOTE: Replacement Variable is required. &3 is the offset you wish to run (0 to -11).
The query is having a & sign in where clause.Part of the q is displayed below
select -------
where -----
and TMP.rel_mth_nbr = &3.
View 1 Replies
View Related
Jul 20, 2006
I�m having this trouble (The product level is insufficient for component "flat file.txt") executing a ssis package using dtexec from a store procedure.
The database is SQL Server 2005 Express Edition with Advanced Services SP1 and Microsoft SQL Server 2005 Express Edition Toolkit SP1.
If anyone knows how to solve this problem i would be very thankful
View 5 Replies
View Related
Jul 27, 2006
We are trying to run SSIS DTSX packages from a VB.Net 2005 application and we get this error : The product level is insufficient for component.
The server is SQL 2005, the clients (for which the VB application is run from) have SQL 2005 Client tools (since there are running XP).
I know this is a known issue, as SP1 corrected the import/export problem in Management Studio, can we expect a similar fix when using SSIS locally on a client's machine via a VB.Net application and SQLServer 2005 assemblies ?
We are currently in the process of migrating our VB.Net 2003/ SQL2000 applications to VB.Net 2005/ SQL2005 and do not want to change the way we process our data, as we expected 2005 version to have the same functionality as 2003.
Thanks,
Patrick
View 4 Replies
View Related
Nov 10, 2006
Hi. I'm using SQL Server 2005 Management Studio to try and run an SSIS package. One step blows up with this error: "The product level is insufficient for component "data conversion 1"". I checked out the thread here: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=112469&SiteID=1&PageID=0
However, after installing SP1, the program is still giving me the error. I'm running the package from my WinXP Pro SP2 workstation. What am I missing? Thanks.
View 6 Replies
View Related
May 19, 2006
I developed some packages using BIDS. I only have the Workstation Components installed on my PC, SQL Server 2005 Enterprise Edition, SSIS, SSAS, etc.. are all installed on the server.
I can run all the packages fine, if I run from my own PC.
I deployed the packages to the server, but when I try to run the packages using SQL Server Management Studio, they don't work.
I'm getting an error message "The Product level is insufficient for component "xxxxx". I get this error for each component created in my package.
All the data files are on the server, even when I run using my own PC.
Any help would be appreciated.
Ercilia
View 3 Replies
View Related
Jun 15, 2006
hi,
I am very new to SSIS. I have created a small application in which the data flow task contains OLEDB source, derived column and datareaderdest.When i run dtexecui.exe and execute the package i am getting these errors
The product level is insufficient for component "Derived Column"
The product level is insufficient for component "DataReaderDest"
But i am not geeting any warning or error when i debug the solution.
Please help me on this.
Thanks in advance
View 6 Replies
View Related
Sep 27, 2006
We've devoted a resource to this today, but I have to believe it's something easy that we're overlooking. The scneario is that we have a production Web application that until last weekend had a SQL 2000 back end. This weekend we installed a new instance of SQL 2005 and everything works (we tested in a sandbox environment, but someone must not have load tested enough) and never saw these exceptions. So, after the upgrade we now receive 100's of thexe SQL excptions per day:A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.)A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The specified network name is no longer available.)Does anyone know what we've overlooked that's causing this issue?Thanks for any help!
View 2 Replies
View Related
Feb 6, 2007
I have the developer edition of MS SQL and applied SP4 to it. Here's what I get when I execute SELECT @@Version:
Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38 Copyright (c) 1988-2003 Microsoft Corporation Developer Edition on Windows NT 5.1 (Build 2600: Service Pack 2)
According to the readme, here are the version numbers for each service pack:
SQL Server 2000 Version and Level
@@VERSION
Product Level
SQL Server 2000 Original Release
8.00.194
RTM
Database Components SP1
8.00.384
SP1
Database Components SP2
8.00.534
SP2
Database Components SP3, SP3a or MSDE 2000 Release A.
8.00.760
SP3
Database Components SP4
8.00.2039
SP4
Do I trust the Version Number or the Product Level? Anyone know what the story is? TIA.
View 3 Replies
View Related
Oct 10, 2006
I developed a package in BIDS which simply runs a query, does a data conversion on one field, then exports to Excel. This works fine in BIDS. When I import the package to the server, I receive the Product Level is Insufficient error for both the data conversion component and the excel destination.
I have verified that SSIS is installed and the service is running. I have verified that SP1 is installed.
Some other things about the environment:
- Running x64 versions of Windows and SQL 2005
- Did not install the workstation tools on the server
Any suggestions?
View 1 Replies
View Related
Aug 11, 2006
I read other threads with this problem and one solution was to install SP1 on the workstation. Our server is running 9.00.2047(SP1) and my workstation SSMS version is 9.0.2047.00 so I'm assuming it's SP1 and I am still getting this error.
To make matters worse, I have jobs set up to run these packages ON the server, but they aren't working either because I have '...error authenticating proxy...Logon failure unknown user name or bad password'. I'm trying to use my Windows login because it has sysadmin rights; I created credentials, assigned them to a proxy under SSIS Package Execution; in the SQL Agent log I get the error '...SQLServer Error: 22046, Encryption error using CryptProtectData.'.
Any suggestions appreciated.
</P
View 5 Replies
View Related
Apr 10, 2008
I have created an SSIS On my PC, That extracts data out of Lotusnotes. When I run it manaully from Visual studion-execute package, it works just fine.
However, when I go tO Management studio, chose the servername, then go to Stored Package-MSDB- And chose Packagename, and hit Run PKG from there, it gives me the error below. Server has 2005 AND IS WINDOWS 2003 OS.
The product level is insufficient for component "datareader source"
Can you tell me why the same pkg will work fine when executed from Visual studio-But when I go the run it from Storedpackages-MSDB-it fails.
View 8 Replies
View Related
Jul 14, 2006
Hi,
I want to call a dll from Stored procedure developed in SQL Server 2005 at configuration level 80. but when I execute the stored procedure I get the following error.
Error Source: ODSOLE Extended Procedure
Description: Invalid class string
Code of stored procedure and vb.net class is given below:
VB.Net
Imports System
Imports System.IO
Imports System.Data
Imports System.Data.SqlClient
Imports System.Data.SqlTypes
Imports Microsoft.SqlServer.Server
Imports Microsoft.VisualBasic
Imports System.Diagnostics
Public Class PositivePay
Public Shared Sub LogToTextFile(ByVal LogName As String, ByVal newMessage As String)
' impersonate the calling user
Dim newContext As System.Security.Principal.WindowsImpersonationContext
newContext = SqlContext.WindowsIdentity.Impersonate()
Try
Dim w As StreamWriter = File.AppendText(LogName)
LogIt(newMessage, w)
w.Close()
Catch Ex As Exception
Finally
newContext.Undo()
End Try
End Sub
End Class
===============================================================
STORED PROCEDURE
Create PROCEDURE [dbo].[PPGenerateFile]
AS
BEGIN
Declare @retVal INT
Declare @comHandler INT
declare @errorSource nvarchar(500)
declare @errorDescription nvarchar(500)
declare @retString nvarchar(100)
-- Intialize the COM component
EXEC @retVal = sp_OACreate 'PositivePay.class', @comHandler OUTPUT
IF(@retVal <> 0)
BEGIN
--Trap errors if any
EXEC sp_OAGetErrorInfo @comHandler,@errorSource OUTPUT, @errorDescription OUTPUT
SELECT [error source] = @errorsource, [Description] = @errordescription
Return
END
-- Call a method into the component
EXEC @retVal = sp_OAMethod @comHandler,'LogToTextFile',@retString OUTPUT, @LogName = 'D: ext.txt',@newMessage='Hello'
IF (@retVal <>0 )
BEGIN
EXEC sp_OAGetErrorInfo @comHandler,@errorSource OUTPUT, @errorDescription OUTPUT
SELECT [error source] = @errorsource, [Description] = @errordescription
Return
END
select @retString
END
View 6 Replies
View Related
Oct 18, 2005
I'm using the import wizard to create a new table from a flat file source. The table gets created but no data gets copied. What's wrong? Here's the report:
View 87 Replies
View Related
Jan 29, 2007
Hello,
I have read previous threads on this, still not working.
New installation of SQL Server 2005 on a Windows Server 2003 box. I have installed SP1 on both the server & the client, do I have to re-create the package?
Thanks in advance,
Dave
View 5 Replies
View Related
Apr 5, 2007
Hi all,
I have created a dts (.dtsx file). which gets the data from my log file and insert into my sql 2005 table. In dts i am using 'Flat File Source' and 'OLE DB Destination' (becoz i need to acess my db remotely). When i execute this through 'SQL Server Business Intelligence Development Studio' it's working fine but when i execute this through my c# code, it throws me an error 'The product level is insufficient for component Flat File Source (1)'.
My c# code :
string strLocalPath = @"d:FTPServiceMyPackage.dtsx";
Application app = new Application();
Package package2 = app.LoadPackage(strLocalPath, null);
// Now that the package is loaded, we can query on
// its properties.
int n = package2.Configurations.Count;
DTSProtectionLevel pl = package2.ProtectionLevel;
DTSExecResult result2 = package2.Execute();
string strErrorDesc = "";
if (result2 == DTSExecResult.Failure)
{
foreach (DtsError local_DtsError in package2.Errors)
{
strErrorDesc = local_DtsError.Description;
}
}
Output of all objects :
n = 0
p1 = EncryptSensitiveWithUserKey
result2 = Failure
strErrorDesc = The product level is insufficient for component "Flat File Source" (1).
Please help me to solve this problem ASAP.
Thanks
Harsh
View 3 Replies
View Related
Jan 30, 2007
Hi,
I have created a Integration Services package that takes a table in a database, and transfers it to a flat file. This package has successfully run through visual studio 2005 as a .dtsx package, and given the output that I expected.
However, now, I am trying to excecute the package (as xml) using C#, and I am receving this error:
Error in Microsoft.SqlServer.Dts.Runtime.TaskHost/DTS.Pipeline : The product level is insufficient for component "Flat File Destination" (31).
I do not understand how a working package would have this kind of error.
Considering that it runs when I do not use C# code to execute the package means that I have SSIS properly installed, and I have the proper versions (or it should not execute ever). I have SP1 for both SQL Server 2005, and Visual Studio 2005 installed.
Other packages that I have created using C# code also have the same problem.
Any assistance would be greatly appreciated.
View 5 Replies
View Related
Apr 17, 2007
Hello!
I have a application where users are supposed to edit data from a table in a datagrid.
I want to use a dropdownlist to let the user choose a table to edit.
The users are members of different windows-goupes and different users have only access to edit there own tables. Let's say that they own data in different tables.
Is it possible to use windows authentication to find out what tables to show in the dropdownlist?
If it is, how do I get the names of the tables?
Best regards
Per
View 3 Replies
View Related
Nov 20, 2007
Hello,
I have a production machine and a developer machine with Ms SQL Server Management Studio I connected remotly to the integration services hosted in the production machine. Then I exported a package and then, when it was executed, I had the following error:
"the product level is insufficient for component excel source"
So I thought that it was because the excel file that I was trying to upload was in the developer machine, so I pointed the Excel Data Source to a shared folder but I still having the same error.
I have read another posts but I'm afraid because the conclusion is that I have to install the SSIS in the developer machine, I hope I misunderstood the solutions!!!
please help, thanks
View 7 Replies
View Related
May 22, 2008
I am trying to add a linked table to my server, it is an access table.
Here is the code i am using but i get an error:
EXEC sp_addlinkedserver
@server = 'AITdb_be2',
@provider = 'Microsoft.Jet.OLEDB.4.0',
@srvproduct = 'Access',
@datasrc = '\kcapp03deptsCommonEIQAIT DBTestAITdb_be.mdb'
GO
-- Set up login mapping using current user's security context
EXEC sp_addlinkedsrvlogin
@rmtsrvname = 'AITdb_be2',
@useself = 'false',
@rmtuser = 'Admin',
@rmtpassword = ''
GO
-- List the tables on the linked server
EXEC sp_tables_ex 'AITdb_be2'
GO
ERROR:
OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server "AITdb_be2" returned message "The Microsoft Jet database engine cannot open the file '\kcapp03deptsCommonEIQAIT DBTestAITdb_be.mdb'. It is already opened exclusively by another user, or you need permission to view its data.".
Msg 7303, Level 16, State 1, Procedure sp_tables_ex, Line 41
Cannot initialize the data source object of OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server "AITdb_be2".
View 3 Replies
View Related
