We have existing users who use a remote desktop connection to a Windows 2003 server to access the Adagio modules. With one of our new users to this process, when we open any of the Adagio modules, we get an error message stating the following:

‘unable to load registration dll’

The mapped drives and permissions seem to be exactly the same for the successful users logging in and the one new one who cannot. We have checked that the existing remote access users can still connect via remote desktop connection and they are able to do so without the above error message.

What does this error mean and how can we correct this problem?

Thank you,
Tanja

Hi, Tanja,

Check to make sure that this user has the same access to the Windows\System32 folder and the files in it that the other users have.

Hi,
We have checked the system32 folder and the permissions are the same as the other users. Even when giving the new user full access to the system32 folder, the error message still appears. Is there anything else we can check or try?

Thank you,
Tanja

Hi Tanja,

Is this "new user" running Vista or Windows 7?

Hi Andrew,

The new remote user is using Windows XP, which is the same as me and I am able to successfully connect via remote desktop connection.

Thanks,
Tanja

Is your Windows 2003 server a terminal server?

The WIN2003 server is a terminal server.

Our IT Manager is also unable to connect to Adagio via remote desktop and he has full rights and access to everything. He's compared my account permissions and rights to the new user's and they are the same.

The program tries to load but cannot get past the error message ‘unable to load registration dll’.

We're not sure what else to try at this point.

Thanks,
Tanja

A shot in the dark, but may be worth a look ...

Do you have any type of Internet Security product installed ? Maybe it's the setings for the FW or AV on-access/background scanning that's different ?

Do let us know when you get it solved.

Regards, Pete

Hi, Tanja,

In that environment, the problem must be a rights issue. All Adagio modules refer to that one file and it is the only one installed on the system. If all of your other users can run Adagio without receiving the error, you need to determine what the difference is between the user that can't run Adagio and the users that can.

You might also want to run ChkSys (located in the Softrak\System folder) while this user is logged on through remote desktop. There is a Check R/W Status button that can be used to determine the user's access to the common Adagio Folders. It's important that you are logged onto the workstation as the Windows user that would be running Adagio when you run ChkSys.

If their rights to the folder are okay, there must be something else that is different with the individual user than the others.

Tanja,

It would be interesting to know the answer to Peter's question also.

Hi again,

We tried to run chksys, but when logged into the server as the user thru a terminal session, the chksys cannot be run while browsing thru the mapped drive (I: is mapped to our accounting software, the softrak folder etc), it gives an error of “you do not have the appropriate permissions to access the item”. However, when we browse using My Computer and not the mapped drive, chksys does run and we get this report…

STATUS OF COMMON ADAGIO FOLDERS ===

C:\WINDOWS\system32 --- ** Folder is not writeable.

C:\Documents and Settings\fverhagen\WINDOWS\CRYSTAL --- ** Folder doesn't exist.

I:\qrasp --- Read/Write Status is OK for this folder.

E:\finance\ACCOUN~1\SOFTRAK\system --- Read/Write Status is OK for this folder.

E:\finance\ACCOUN~1\SOFTRAK\dict --- Read/Write Status is OK for this folder.

E:\finance\ACCOUN~1\SOFTRAK\system --- Read/Write Status is OK for this folder.

=== STATUS OF ADAGIO RECENTLY USED DATA FOLDERS ===

AL: i:\data\society prior years\gl\gl_2006-2007 --- Read/Write Status is OK for this folder.

AL: i:\data\society prior years\gl\gl_2005-2006 --- Read/Write Status is OK for this folder.

AL: i:\data\society prior years\gl\gl_2004-2005 --- Read/Write Status is OK for this folder.

AL: i:\data\johnson street prior years\gl_2006-2007 --- Read/Write Status is OK for this folder.

AL: i:\data\johnson street prior years\gl_2005-2006 --- Read/Write Status is OK for this folder.

AL: i:\data\accountg\johnson st partnership --- Read/Write Status is OK for this folder.

AL: i:\data\accountg\victoria cool aid society --- Read/Write Status is OK for this folder.

AP: i:\data\society prior years\2008 --- Read/Write Status is OK for this folder.

AP: i:\data\society prior years\ap\ap-2006_2007 --- Read/Write Status is OK for this folder.

AP: i:\data\johnson street prior years\ap-2006_2007 --- Read/Write Status is OK for this folder.

AP: i:\data\johnson street prior years\ap-2005_2006 --- Read/Write Status is OK for this folder.

AP: i:\data\society prior years\ap\ap-2005_2006 --- Read/Write Status is OK for this folder.

CR: i:\softrak\crwin\samdata --- Read/Write Status is OK for this folder.

=== STATUS OF ADAGIO "EZTASKS" FOLDERS ===

i:\softrak\system --- Read/Write Status is OK for this folder.

=== STATUS OF ADAGIO "CURRENCY" FOLDERS ===

i:\softrak\system --- Read/Write Status is OK for this folder.

We then ran the chksys for the user who is able to access remotely and noticed that that C:\\WINDOWS\system32 folder for them indicated that read/write status is OK. While logged into the remote desktop session as the new user, we then went to the system32 folder and in security we created a new user for this individual with full access to the folder. When we re-run chksys for this new user, we get the following:

=== STATUS OF COMMON ADAGIO FOLDERS ===

C:\WINDOWS\system32 --- Read/Write Status is OK for this folder.

All other statuses were the same as the first report.

The permissions in system32 of the successful user and the new user now appear to be the same and the chksys results are the same, however when we try to run Adagio remotely while logged in as the new user, we still get the "unable to load registration dll" error message. So we've changed the permissions and given the new user full access to system32 (which is more than the successful user has) but still cannot access Adagio via their remote connection.

Not sure where to go from here. We appreciate all the help and suggestions and if anyone has anything else to recommend we will certainly try it!

Thanks,
Tanja (and Ed)

Hi Pete,

We do not have any type of internet security product installed. And our IT guy doesn't think it has to do with the FW or AV as I can successfully login remotely to Adagio on the same computer that our new user cannot.

Thanks for the thoughts though.
Tanja