Unable to export through TS

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi all. I have a problem that I have been going crazy over for the past
couple of weeks. Here is how it started: I had a program that I designed on
Windows 2000, VB6 sp5, and Crystal Reports. I purchased a new computer with
Windows XP. I loaded everything on to my new computer and then ran the SP6
upgrade for VB on my new computer and on the server. When I installed the
program on the Server (Windows 2000)(under Add/Remove Programs), things went
ok until my users using
Terminal server tried to log in. They would receive the following errors:
1) Run-time error 339: Component ssdw3bo.ocx or one of it's
dependencies...etc etc
2) Run-time error 419: Permission to use object denied.
After much searching and just plain trying everything, I found that by going
to every dll and pulling up the properties box, then going to the Security
tab and checking the "Inherit permissions from etc etc" worked and the
terminal server users were able to get in to the program. Now however, I
have another
problem. The terminal services users can pull up a Crystal Report and export
the report to every other file type EXCEPT pdf files. They get the popup box
to select the page but then there is no box to allow them to save the file.
I have registed my DLL's and check everything I can possible think of and I
have been looking for solutions for this problem but have found nothing yet,
though I have seen that there are many other people out there who are
experiencing the same problem. Any help or ideas would be so GREATLY
appreciated!!

P.S. I did post this to the Visual Basic newsgroup under deployment, then
thought better and put it under Crystal. But now I am thinking that it is a
permission issue rather than any of my previous choices.
 
Melody said:
Hi all. I have a problem that I have been going crazy over for the past
couple of weeks. Here is how it started: I had a program that I designed on
Windows 2000, VB6 sp5, and Crystal Reports. I purchased a new computer with
Windows XP. I loaded everything on to my new computer and then ran the SP6
upgrade for VB on my new computer and on the server. When I installed the
program on the Server (Windows 2000)(under Add/Remove Programs), things went
ok until my users using
Terminal server tried to log in. They would receive the following errors:
1) Run-time error 339: Component ssdw3bo.ocx or one of it's
dependencies...etc etc
2) Run-time error 419: Permission to use object denied.
After much searching and just plain trying everything, I found that by going
to every dll and pulling up the properties box, then going to the Security
tab and checking the "Inherit permissions from etc etc" worked and the
terminal server users were able to get in to the program. Now however, I
have another
problem. The terminal services users can pull up a Crystal Report and export
the report to every other file type EXCEPT pdf files. They get the popup box
to select the page but then there is no box to allow them to save the file.
I have registed my DLL's and check everything I can possible think of and I
have been looking for solutions for this problem but have found nothing yet,
though I have seen that there are many other people out there who are
experiencing the same problem. Any help or ideas would be so GREATLY
appreciated!!

P.S. I did post this to the Visual Basic newsgroup under deployment, then
thought better and put it under Crystal. But now I am thinking that it is a
permission issue rather than any of my previous choices.
Click to expand...

This is the first time I have posted to this forum. So if I didn't follow
protocol in replying, sorry.

When my IS team installed VB6 applications that use Crystal reports onto our
Terminal Server (TS deployed in application server mode) we experienced a few
similar issues. It has been awhile since we successfully installed our VB6
applications, but two things come to mind:

1) Each export format in Crystal has its own .dll. Make sure your
application deployment package contains all (and the latest version) of the
crystal dll's for the export formats you want available to your users.

2) Make sure Acrobat is installed on the Terminal Server (we initially
forgot to do this- Duh!)

Likely you have already taken these basic steps. If not, I hope this was
helpful.

Also should mention that we have experienced differences in the way forms
are rendered to pdf from our VB6 applications depending on which version of
Acrobat is installed (we have stuck with version 6 since version 7 messes
things up a bit).

- Tom
 
Back
Top