Prompting for Library at Logon

[wooddsw]

I'm currently in the process of decommissioning AccPac due to a merger. My current configuration is an application server which connects to our may SQL server that houses the databases. I'm attempting to install a local copy of SQL2000 on the app server and ultimately disconnect it from the main database server so we can still maintain it for historical information. I've accomplish all that and I'm now trying to get the application running locally on the server. I've run through the steps to migrate the data between SQL Server successfully and have also run the workstation setup on the local app server. Now when I attempt to logon, after entering the ADMN credentials I'm being prompted with a file open for some library file type. The only thing that enumerates are:

ADDPROP5.FLL
FOXTOOLS.FLL
JKEY.FLL
SBTTOOLS.FLL

I've selected each of these with no success. Cancelling out of that I get:

ERROR:12 Variable not found
Called from g_setlib line number:90
Program code causing error:
DO e:\accpac\pro73\sbtw.exe

Ignorning the above I get a message that FOXTOOLS.FLL isn't loaded. I've gone back in and restarted selecting FOXTOOLS and ultimately also SBTTOOLS and then I get the following error:

ERROR 1: File does not exist
Called from : l_dfmsbt line number:2121
Program code causing error:
cc_count=substr(cc_result,at(',',cc_resutl,4)+1)


I've also modified the Temp environment variables appropriately. It would seem that my pathing is not quite right locally when it says it cannot locate the necessary files.

Any guidance would be greatly appreciated.

 

[ettienne]

Not many Accpac Pro people here, but I would guess you have a bad install. Did you do an install from CD or did you copy of the program files from the other server?

 

[wooddsw]

I've basically taken the current production server image and installed it onto a test box using Symantec Server Recovery product. I changed the computer name and IP so it didn't conflict with the current production box.

Installed a separate instance of SQL2000 on that server and used Sages document on how to migrate data between SQL servers.

Working totally off the wire right now.