7077 The Advantage Data Dictionary cannot be opened
7077 The Advantage Data Dictionary cannot be opened, this is one of the errors you might receive when running an application against an Advantage Database Server.
We have a medical application called “Æskulap” developed in Denmark by Medcom . This application was running just fine on our Windows 2003 server, then we had to move the application and the Advantage Database Server on a newer Windows 2008 R2 Server because the old machine was now out of warranty and it started also to have some small issues. So we decided to move the Advantage Database Server and Æskulap from the old Windows 2003 machine to a new hardware.
The migration process was quite simple, install a new Advantage Database Server on the new machine, copy all the data from the Æskulap folder to the new server and simply start working from the new share on the new server.
The problem started to appear soon after we started the Æskulap on more than one machine. The issues we encountered were :
– If Æskulap started we started receiving the “7077 The Advantage Data Dictionary cannot be opened” error.
– When the Æskulap started, it started very slow
– Æskulap was very slow, moving between menus and processes inside the application took much more time than usual.
I tried to research the problem on Google and none of the solutions applied to me and as I did not know what else I could do I decided to call the support line.
I called Profdoc support department and they immediately told me that this is a well known issue and it is a communication problem between the client and ADS server. I told them that this can not be the case because I was getting the 7077 error also when I tried to start the Æskulap from the local machine, there where both Æskulap and the Advantage Database Server was installed.
Then I was told to check my firewall, check the permissions and many other “might be this” solutions. Nothing helped and the guys from Profdoc did not even try to look at some log files or try to start e debugger or something like this … nothing. Even more, they saw that I did not yet activated my Windows license and they started bragging that it is therefore my software is not working and I was told they will cease to give me support until I will activate my windows.
Anyway, after more than one hour on the phone with the Profdoc support line (server management) they gave up and I was on my own.
So my problem was still there, I was still getting the 7077 error sporadically. I observed that if I tried to start Æskulap and got the error, then tried to start it again in a few seconds the error was gone and I could log on.
I started looking for documentation on Advantage Database Server and settings for this and I found out that normally no INI file is needed for it in order to run but it can use an initialization file, ads.ini, to override specific default settings such as the Advantage server type.
Looking on the old server I could see no ads.ini file and I decided to make one myself.
“Windows – In order for the ads.ini file to be used, it must be located in the application directory, the Windows directory, the Windows System directory, or the client’s search path.” says the ADS Developer Zone on their site.
My file then looks like this :
[appserver.mydomain.com] LAN_IP=10.10.10.10 LAN_PORT=6262 RETRY_ADS_CONNECTS = 1 [DRIVES] S:=\medcomaeskulap [appserver] LAN_IP=10.10.10.10 LAN_PORT=6262 RETRY_ADS_CONNECTS = 1 [DRIVES] S:=\medcomaeskulap
I did it like this with both FQDN and Netbios name because I still have some old machines on the network and I did not want to have any other issues later. All my machines have mapped the S: drive by a GPO.
After I added the ads.ini file everything started working like a charm !
Conclusion: When running Advantage Database Server on a Windows 2008 R2 server you most likely will need an ads.ini initialization file in order to have a working system. Also after adding the ads.ini file, the Æskulap was much more faster and nobody complained about speed anymore.