Dear prk

I am sorry to hear that you have had export issues that could never be resolved - have you contacted us for help on this issue?

Regarding your current problem with trying to run QRW on a Win 2000 Server - in order for a workstation to access QRWIN, a workstation setup must be done on that workstation. QRW should be fully installed onto the Server that these workstations will be accessing. Make sure that when performing the install and the w/stn setup that all required network/workstation rights are available, even if you have to give all rights when installing, then set them back to their original settings once finished.

If QRW is unable to see the ACCPAC.ssi database file, do you have the "list files of type - All Files" option selected on that window? That is what is sometimes required in order for you to see that file. This file exists in the QRW directory on the system that you installed QRW to. If QRW was not installed on this 2000 Server, then that is likely a good part of the problem, but not all of it.

I don't know much about Terminal Server, but I do know that if these offsite users wish to access QRW and the associated reports, then those machines must have at least the workstation setup done on them in order to do so, however, you may also require a QRW Lanpak to run QRWIN with the proper multi-user licensing.

I hope this helps.

Terminal Server works very differently than the usual NT/Novell server setup. The Crystal Reports engine which powers Quik Reports for Windows and reports for many other applications requires the installation of files to the c:\windows\crystal directory, such as exporting DLLs and other necessary files (PDBSSI.DLL is one of these files). In addition, other files are installed to the c:\windows\system directory, such as the crpe.dll file with a 10/2/1995 file date.

If you are running Windows 2000 as a Terminal server, the workstation setup will likely not install the required 'local' files as the install function expects to see the "c:\windows\..." structure.

A workaround for this is to reinstall Quik Reports for Windows to the same location on the network drive (ie K:\qrw) from each workstation that will use QRW. In effect, this will not change the programs (basically it's reinstalling), but during the install, the required files that are installed to a users C: drive will be put into the proper Terminal User directory.

Should this not work, then something has not been configured correctly with the network for the users to have files installed for their 'local' machine.

More information has been made available to do with printing in TS using Crystal or any applications that use Crystal to report with (this included QRWIN). This information is posted on the PlusCommunity discussion forum at: www.pluscommunity.com . It may or may not have been on the Seagate site at the time of your original problems, but nevertheless I hope it can assist you now.

Possible problems when Users are logged in to NT or W2K Terminal Servicer/Services are that they cannot print reports. They may or may not get errors to do with the reporting .dlls not being found.

By default, Seagate Crystal Reports expects the export DLLs to be located in %systemroot%\Crystal. On a Terminal Server or Citrix computer (respectively), the DLLs are located in the following directories:

\Wtsrv\Profiles\<user>\Windows\Crystal
\Wtsrv\System32

Check out this tech article from Crystal:
http://support.crystaldecisions.com/kbase/c2006348.asp

While this article pertains to Crystal Info, the issue with the Crystal Reports runtime is the same. They offer three solutions, the first is not applicable as you are only using the runtime, not installing Crystal Info or Reports. The other two are to copy the dll's to the user profile folder as suggested (this is the preferred solution for Adagio), or to copy into the \WINNT\System32 (or ntsrv\System32 for Citrix).

This will take care of the Crystal printing issue.

For example:
Copy the CRYSTAL directory from the User?s system?s local C:\Windows\Crystal, or C:\WINNT\Crystal to the Terminal Services User Profile.

Other information?
TS creates virtual directories for each user, to simulate a ?local? drive when using terminal services. In the user path, there is likely the following structure:

?Wtsrv\Profiles\<USER>\?\documents & settings\Windows\..."

For Adagio, what has been suggested is to copy the user?s local CRYSTAL directory (if a wksetup was done on that workstation?s local hard-drive), and copy it to the TS virtual 'Windows' directory for that user. You must do this for every user that needs to print from Adagio when logged into TS. The CRYSTAL directory must be in the WINDOWS directory. So, for example, the new pathing after copying the Crystal directory to TS would be:

?Wtsrv\Profiles\<USER>\?\documents & settings\Windows\Crystal...?

All the files residing in the original Crystal directory would now reside in this User?s TS Virtual Crystal directory.

(PS The actual path information may vary slightly, but the point is ? the Crystal directory must be under the User?s virtual ?Windows? directory.)

After discussing this further, we thought there may be other files that get missed during the original wksetup ? so if you still have problems, go to each users? virtual directory on the TS and look for:

?P2QRTSSI.DLL? This file needs to be in the User?s Windows\System directory
?REGSSI32.DLL? Needs to be in the User?s Windows\System directory
?CRPE.DLL? Needs to be in the User?s Windows\System directory (Adagio Receivables, Checks)
?CRPE32.DLL? Needs to be in the User?s Windows\System32 directory (Our 32-bit apps)

If these files are not there, you may have to copy them over into these directories as well.

Hope this helps.

For more information on printing with NT Terminal Server and/or W2K Terminal Services:

http://search.microsoft.com/us/products/windows/windows-2000/SearchMS25.asp?

Regards

Softrak Support