February 3, 2012 at 10:50 am
Hi all, errors out as follows when attempting import:
"Test connection failed because of an error in initializing provider. Cannot start your application. The workgroup information file is missing or opened exclusively by another user"
I'm using SP3 which should get me in, and my password is correct as I can access via....Access!
I have a feeling it might be a provider issue, but the only option the import wizard gives me is 'Microsoft Access', which I assume is Jet 4.0.
Any idea how to complete this import?
February 3, 2012 at 12:18 pm
Access 97 is back in time somewhat, so not sure this will work for you, but for getting Excel info in, we are using Native OLEDB\Microsoft Office 12.0 Access Database Engine OLEDB provider and in extended properties I'm setting "Excel 12.0"
Not sure what v Access 97 would be but you may play around with putting different version numbers into extended properties.
and might I just say, stupid workgroup file. always hated that thing.
February 3, 2012 at 12:29 pm
Not sure you understand, I'm simply using the 'Import' wizard to try to get the data in. I've looked at the Datalink Properties, the wizard uses Jet OLEDB but the Extended Properties field is empty.
I've also (within Access) upgraded the file version to Access 2002, still no go.
February 3, 2012 at 1:01 pm
long time I used Access97 or 2002....but iirc wasnt there some form of "Workgroup Security"...maybe a long shot but have you created any Access security groups?
________________________________________________________________
you can lead a user to data....but you cannot make them think
and remember....every day is a school day
February 3, 2012 at 2:18 pm
Jake Shelton (2/3/2012)
Hi all, errors out as follows when attempting import:"Test connection failed because of an error in initializing provider. Cannot start your application. The workgroup information file is missing or opened exclusively by another user"
I'm using SP3 which should get me in, and my password is correct as I can access via....Access!
I have a feeling it might be a provider issue, but the only option the import wizard gives me is 'Microsoft Access', which I assume is Jet 4.0.
Any idea how to complete this import?
For importing a ACCESS file:
Make sure nobody/no application is accessing that access file. Make sure it is closed.
Were you able to browse the file/file location?
Try an Access database with password and without password.
Preview the data.
And you will be good to go from there.
Hope this helps you out. Drop a note of your experience.
Thanks.
February 3, 2012 at 2:26 pm
I can browse the data in BIDS, but don't know enough SSIS to copy the entire DB, I can just preview one table at a time.
February 3, 2012 at 2:49 pm
Jake Shelton (2/3/2012)
I can browse the data in BIDS, but don't know enough SSIS to copy the entire DB, I can just preview one table at a time.
To copy all the tables from access to another database..you need to do one table at a time.
You cannot create a single oledb source for all the tables in the access database.
For each table to copy you need to create a single OLEDB source.
Hope this helps you out to work with SSIS in importing the data from access tables.
February 3, 2012 at 2:57 pm
There's got to be a way to copy the whole DB at a time, there are hundreds of separate tables in it.
February 3, 2012 at 3:03 pm
Jake Shelton (2/3/2012)
There's got to be a way to copy the whole DB at a time, there are hundreds of separate tables in it.
if this a one time operation to move Access to SQL then the following may help:
http://support.microsoft.com/kb/237980
________________________________________________________________
you can lead a user to data....but you cannot make them think
and remember....every day is a school day
February 3, 2012 at 3:04 pm
What is your destination database like SQL Server...oracle..db2???
February 3, 2012 at 4:28 pm
I'm afraid you're in troubles. I'll try to explain you this item as clear as my limited english let me do.
The message "The workgroup information file is missing or opened exclusively by another user" means that the Access file was originally created assigning users and roles for each of its objects wich were stored in, yes, workgroup information files.
Perhaps in some point of the time the Access file was migrated to a new computer, but not so the workgroup information files. If you don't have any way to recover these files, but you have at least MS Access 2000, you can change the owner of all the objects to the default user "Administrator" and to the default group "Administrators" and try to import again.
If my memory isn't failing yet, after opening the file with Access you will find this option in menu [Tools] - [Security] - [Users and Groups].
I hope this could be useful for you.
February 3, 2012 at 4:42 pm
I do indeed have the Workgroup file, it's name is sytem.mdw. I've "successfully" added myself to the the group using the Access utility you mentioned....
but no change. Still the same error.
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply