Unable to selfregister msjro.dll

[ulfmalmros]

I have created package for distribution of a VB6 application, but the end user claims that it is not working.
The database is opened in the application in the following statement

set dbTarg=Workspaces(0).OpenDatabase("D:\Databases\TT Mätdon.mdb",false,false)

When they are running the application it asks for an ODBC driver, but when I test it it works OK. The Path to the access database is OK.

In the installation log it says:

*** ERROR: LoadLibrary() failed while registering file 'C:\WINDOWS\system32\msjro.dll'
*** DURING THIS ACTION: DllSelfRegister: "C:\WINDOWS\system32\msjro.dll"

*** ERROR: An error occurred while registering the file 'C:\WINDOWS\system32\msjro.dll'
*** ERROR: (User Responded with 'Ignore')
*** DURING THIS ACTION: DllSelfRegister: "C:\WINDOWS\system32\msjro.dll"

I has asked if there are any other applications running but there are not I get as an answer.
The log says:
*** ERROR: C:\WINDOWS\system32\expsrv.dll
*** ERROR: The destination file in in-use. Please ensure that all other applications are closed.
*** ERROR: (User Responded with 'Retry')
*** DURING THIS ACTION: SystemFile: "C:\WINDOWS\system32\expsrv.dll"

*** ERROR: C:\WINDOWS\system32\expsrv.dll
*** ERROR: The destination file in in-use. Please ensure that all other applications are closed.
*** ERROR: (User Responded with 'Ignore')
*** DURING THIS ACTION: SystemFile: "C:\WINDOWS\system32\expsrv.dll"

*** ERROR: C:\WINDOWS\system32\expsrv.dll
*** ERROR: The destination file in in-use. Please ensure that all other applications are closed.
*** ERROR: If you ignore a copy error, the file will not be copied. The application may not function properly as a result. Do you want to ignore the error?
*** ERROR: (User Responded with 'No')
*** DURING THIS ACTION: SystemFile: "C:\WINDOWS\system32\expsrv.dll"

*** ERROR: C:\WINDOWS\system32\expsrv.dll
*** ERROR: Out of memory trying to copy the file.
*** ERROR: (User Responded with 'Retry')
*** DURING THIS ACTION: SystemFile: "C:\WINDOWS\system32\expsrv.dll"

*** ERROR: C:\WINDOWS\system32\expsrv.dll
*** ERROR: Out of memory trying to copy the file.
*** ERROR: (User Responded with 'Ignore')
*** DURING THIS ACTION: SystemFile: "C:\WINDOWS\system32\expsrv.dll"

*** ERROR: C:\WINDOWS\system32\vbajet32.dll
*** ERROR: The destination file in in-use. Please ensure that all other applications are closed.
*** ERROR: (User Responded with 'Ignore')
*** DURING THIS ACTION: SystemFile: "C:\WINDOWS\system32\vbajet32.dll"

The application is installed on a W2K server.

Thank you in advance

Ulf Malmros

[RobDog888]

What installer are you using? Did you include MDAC in it?

Moved

[ulfmalmros]

I am using Visual Studio 6.0 "Package and depoyment wizard." It worked fine when I installed it on a XP computer.

Thanks

Ulf

[RobDog888]

It looks like you are using DAO to connect to your access database. DAO is old technology and ADO is really better.

If its prompting them for a ODBC datasource then is the databasae in the expected location?

[ulfmalmros]

Yes, the database is in the expected location

//Ulf

[RobDog888]

Ok, then if the user installed your app under admin credentials or not. They may not have permissions to access the Windows directory for registering files as the error list shows its not just mdac but all files.

Also, the app is currently running during the install. Probably crashed and still running in the background so the user doesnt think its running and tries to install your app. Thus the errors in trying to overwrite the files in use.

Are you trying to distribute Access as in the program itself?

[ulfmalmros]

I assume that the installation is done under admin credentials because he who has done it is responsible for the server and other dll:s is registered OK.

I agree that another application must be running and using these DLL:s because the installation log says that they are in use. Unfortunatly I get the answer that no other application is running.

The Access databases is not distributed in this installation. They are already there. The actual app should only collect data from two Access databases and update the third.

Thanks

//Ulf

[RobDog888]

Ask the user to look in the task manager to see if the exe can be located under the running processes tab. If its found then its running and can be terminated from there.

Does their databases have any login credientals or different versions then what you tested on? Can you get a copy of theirs for testing to see if you can connect to it on your system? Are their databases the same version as your test ones?

[ulfmalmros]

I has assumed that he knows what he is doing. For me it would be the natural place to look in but I shall ask him tomorrow.

There are no login credentials to the databases and they are both Access 97 databases, same as in the test environment.

My problem is that my client has outsourced it to a bigger IT-company and they have several clients running applications on that server. My suggestion is still that they install the application when they had the server down for maintenance and before they allow the users to login.
A workaround would be for me to make a new package and install tje msjro.dll in the apps path because then no other application would be using it.

Thanks very much for yor help

//Ulf

[RobDog888]

You should not be distributing the msjro (Microsoft Jet and Replication Objects Library) file because its part of Access and is illegal to distribute.

[ulfmalmros]

MSJRO.DLL is also a part of VB6 Enterprise edition and is legal to distribute together with applications developed in a licensed copy of VB6EE.

[RobDog888]

If you are not distributing MDAC (as mentioned earlier) then you can not distribute it by itself. Either rely upon Access being installed or distributre the latest MDAC and install under an admin account while no other processes/users are using he files.

[ulfmalmros]

They are running two access applications today (at least). That I know because my application should transfer data between these databases. MDAC should be installed.

[RobDog888]

Well "should be" is an assumption that should be confirmed. Download the Component Checker utility from MS to determine what version of MDAC is installed.

[ulfmalmros]

I have no access to the server and no possibility to check anything I'm sorry. it should be an advantege if I had.
The latest agreement is that they will shut down the server this evening and perform a new installation when only admin is logged on. That is what I wanted the whole time.

Thanks

//Ulf

[RobDog888]

Its usually the way things go. Network admins dont want to listen until they have exhausted their possibilities and then they say "ok we will try it your way".

[ulfmalmros]

I agree with you 100% because this morning I received a message that the installation failed again. The server was not restarted before the installation because it was restarted saturday morning. What do I say??

[RobDog888]

What is the Server OS? Is it running Terminal Services?

[ulfmalmros]

Server OS is Windows 2003 and it is not running Terminal Services

Thanks

//Ulf

[randem]

They are running two access applications today (at least). That I know because my application should transfer data between these databases. MDAC should be installed.

Yes, but not the version you need... BTW, I believe you need the SP for Jet Replication installed along with the MDAC. I would say MDAC 2.0.

[RobDog888]

Since its server 2003 it should have SP-2 and also have MDAC 2.8 on it.

[randem]

But it will still not have what he needs...

[RobDog888]

Well he needs 2.8 that comes with the Server 2003 OS install as 2.8 SP-1 and any other previous version of MDAC is not installable on Server 2003.

http://msdn2.microsoft.com/en-us/library/ms810805.aspx

So trying to install a component of it will also fail.

[ulfmalmros]

Thanks for the information. I had a discussion with the server admin about the possibilities to install the new MDAC version. He says that it will be done as soon as the server is brought down for maintenance.
While waiting I have installed the application on a client (XP) that can open the database on the server. It works as it is supposed to do.

Thank you very much for your help

//Ulf

[randem]

The he will need this also

Jet 4.0 Service Pack 8 (SP8) for Windows Server 2003 (KB829558)

[ulfmalmros]

Thanks

//Ulf