Crystal 7 on W2K3TS

[AKPolarBear]

Does anybody access Crystal 7 from W2K3SP1 Terminal Server?
Our Macola 7.6.100a/Crystal 7 run on W2K servers but are accessed by users from the W2K3TS.
Macola & CR7 we set up on the Terminal Servers per the normal Macola instructions. Macola users have no issues and so far, nor do queries from Excel.

I appear to be having some sort of access/permission issue (no errors generated however) in several areas one being some reports do not run correctly. The other is related to printing. We still have a parallel NT domain set up and the reports run ok from there.

I'm wondering if CR7 is just not compatible with W2K3 and that is the whole issue.

 

[NEmacGuy]

Find the %sytemroot%\windows\crystal folder and copy the contents to your crystal foler, ot if you want to get difficult you can copy it to each users windows directory under their profile.

Does it work when logged in as Administrator ???
If so go to help and there is an option that shows you the dll, ulf's and other controls loaded, these files have to be in a path that can be acessed by a user. I like moving them into the crystal folder.

 

[AKPolarBear]

A copy of the Crystal directory is in each user folders under their windows directory.

I did notice a report failure under admin but I'll need to confirm that first. It was from the server and not through a session.

I'll check the dll paths.

 

[bruggles]

Specifically we copy the Crystal Folder mentioned above to the users HOME folder, under their Windows folder and it seemed to fix.

Example H: (mapped network drive to users home folder aka My Documents)

H:\Windows\Crystal

Then tell them not to delete it.

Hope this helps

 

[stravis]

If you use bruggles solution, you must make sure that the home folder is hosted locally. If the home folder is on another server, then not all of the DLLs included with Crystal will be able to run. I don't remember which features are a problem, but it is better to avoid the problem altogether.

Scott Travis

http://www.infoSpring.net

 

[AKPolarBear]

I copy the Crystal folder into the users profile location on each of the terminal severs. Same as with NT TS.

I am wondering if it's just the a version incompatibility between Crystal 7 and Server 2003? The Crystal program files are on a W2K server with the Macola Program and are accessed from the Terminal Servers same as Crystal.

 

[dgillz]

Crystal 7 is 10+ years old. Windows 2003 server by definintion is several years younger. Why are you still on Crystal 7? Why not download a 30 day trial of Crystal XI and see if you still have this problem?

Software Sales, Training, Implementation and Support for Macola, eSynergy, and Crystal Reports

http://www.gainfocus.biz

"A fine is a tax for doing wrong. A tax is a fine for doing well.
" - unknown

 

[stravis]

Windows 2003 Server is more secure by default. You can not just install applications and expect them to run in every situation. I can tell you that I have several clients running Crystal 7 in Windows 2003 Server Terminal Sessions without any issues. On several occasions I have had to modify the configuration of Windows 2003 Server to allow programs to run. The most common issues are with registry permissions and DEP (Data Execution Prevention).

Perhaps you could help us by providing more detail on the exact nature of the problem you are having, citing specific examples.

Scott Travis

http://www.infoSpring.net

 

[AKPolarBear]

-Some reports run without error
-Some reports run but only return field information and no data (zeros') for any formulas used in the report
-Some reports do not run

The above applies to some users but not all. This may be because not all users run the same reports. Admin can run reports.

One common complaint is that when users change printers, the report kicks them out of Crystal with no error message.
As Admin, I change the printer and then they can run it without problem.

We use AD but all the users are currently in the same group except admin. The AD is on a W2K server.

The Macola and SQL servers are currently not part of the new W2K domain but are in an NT domain that is being replaced. One thought is to move them into the new domain now instead of later when the PDC and BDC's are turned off or made into member servers. We still have a couple of NT servers in active service.

Macoal appears not to be affected and is running okay fro mthe new W2K3 TS's.

Most of the issues are not applicable in the older NT domain. I think the second one is for at least one user. This could be a SQL related issue.

It really sounds like a permission issue but have reapplied permissions to all the various Crystal folders and reports. That leaves something on the TS. Could be a registry issue.

If Stravis is not having issues after tweaking the W23K server, then that tells me its not a version issue of problematic DLL's or something.

We are not interested in Crystal XI and would probably consider a different report writer first if I could work out the Macola specific functions.

 

[dgillz]

There are no macola specific functions that cannot be done without a regular formula in crystal. This can make for a very long formula however, particularly the numbertodate() workaround.

I can only assume that these formulas would translate just fine to R&R report writer, Actuate, or SQL Server Reporting services.

Software Sales, Training, Implementation and Support for Macola, eSynergy, and Crystal Reports

http://www.gainfocus.biz

"A fine is a tax for doing wrong. A tax is a fine for doing well.
" - unknown

 

[AKPolarBear]

After a short, unplanned distraction (the company was bought out), I am back to chasing this problem.

If a user runs a CR to screen and then wants to print it, when they click on the printer set up icon, the entire crystal screen vanishes away. No trace, nothing left behind. Same as closing the window only faster.

In testing, I have set user permissions to full on some reports to see how they do. Same result.