TOPIC: Failed to open the connection

Failed to open the connection 20 Sep 2007 00:43 #26

  • chris.gardner
  • chris.gardner's Avatar
I installed Logicity on a PC connected to the network. When I try to open the report or run the .rrd file I get the Failed to open the connection. C:\DOCUME~\'user'\LOCALS~1\Temp\'Report Name' …

Is this something you have any insight on?
The administrator has disabled public write access.

Re:Failed to open the connection 20 Sep 2007 17:31 #27

  • aellis
  • aellis's Avatar
Chris,

Here are a few initial suggestions of where I think the problem may be occurring. Try these ideas out and let me know if they help or not:

1. File Path Problem

It could be that the path to the RPT file is different on the client workstation than it was on the system where you originally built the solution file. Try editing the RRD file on the client workstation and browsing for the RPT file again on the File Name tab to see if the path changes. Save the RRD file and try running it again to see if it works now.

I've also had some issues with using UNC paths in the file name in the RRD. If your file path looks like this:

[code:1]\\SERVERNAME\Reports\Report1.rpt[/code:1]

Try to instead map a network drive to the share containing your reports and point the RRD to the mapped drive path to the report.

The other thing I noticed based on your error message is that the computer doesn't appear to be a member of your domain. So when you access the network share you are probably prompted for a user name and password before you can see the files? Make sure you have accessed the network share and provided these credentials before attempting to run the RRD if this is the case.

2. File Permissions Problem

The problem could also be that the client has permissions to see the RPT file listed in the folder, but does not have enough permissions to open the file. The easiest way to rule this out is to log on as an administrator on the client workstation (and as administrator when you are prompted for a user name and password when connecting to the share) and see if you still get the same error.

3. Local Permissions Problem

The last possibility I could think of is that the user may be lacking the permissions on the local computer to be able to properly write files to the temp directory. As with the previous troubleshooting exercise, the easiest way to determine this is to log on as the local administrator user and see if you get the same errors.

Let me know if you need any additional clarification on any of this and if this does or doesn't solve your issue. We'll figure it out one way or another.

Thanks,
Adam

Post edited by: aellis, at: 2007/09/20 10:32

Post edited by: aellis, at: 2007/09/20 10:32
The administrator has disabled public write access.

Re:Failed to open the connection 20 Sep 2007 23:51 #28

  • chris.gardner
  • chris.gardner's Avatar
Your suggestions don't seem to help, but thanks for the reply. Some additional information about the problem may be helpful to you. The computer I am trying to use does not have Crystal Reports. If I create a remote desktop connection to our TERMSERV the user is able to double click the report and it displays. The TERMSERV server does have Crystal Reports on it, that was where I created the report initially.
The administrator has disabled public write access.

Re:Failed to open the connection 21 Sep 2007 18:53 #29

  • aellis
  • aellis's Avatar
Chris,

Alright, I read your post a little closer and I think the "Failed to open the connection" is actually the most important part of the message. What that tells me is that the viewer is not able to connect to the database in the same way it does from your terminal server. In most situations, this is due to an ODBC data source not being set up exactly the same on both computers. Can you go to the Control Panel / ODBC Data Sources on the terminal server and compare to what is present on the client computer and see if any entries are missing?

Thanks,
Adam
The administrator has disabled public write access.

Re:Failed to open the connection 22 Nov 2007 02:16 #33

  • squaremonkey
  • squaremonkey's Avatar
I had the same problem despite the fact that the odbc connections were exactly the same on both computers.

I found that the crystal report, giving me the connection errors, had been created in Crystal version 8.5. The problem was resolved by opening the report in Crystal version 10 and saving it in version 10 format.

Once done, I was able to open without connection errors.

I hope this helps you too.
The administrator has disabled public write access.

Re:Failed to open the connection 28 Feb 2008 21:13 #114

  • tedkitch
  • tedkitch's Avatar
I too am getting this type of error. Here is the text of the error:

Failed to retrieve data from the database.
Details: [Database Vendor Code: -20005]
Failed to retrieve data from the database.
Error in files C:\DOCUME~1\ted\LOCALS~1\Temp\Production Meeting Open Order Report - No Boxes {37B6A001-96BF-4231....rpt
Failed to retrieve data from the database.
Details: [Database Vendor Code: -20005](emailCrystalReport)

I'm trying to exececute the RRD file on a Windows XP machine, using a Merant ODBC driver to connect to a Progress Database. The report in question runs perfectly using the Logicity Desktop, but gives me the previously stated error when I try to execute as an RRD.

I've worked my way through all of the previous suggestions in this series of posts. Currently the report is in an 8.5 format and I've tried saving it under v2008 and I get the same error. I have checked the ODBC settings to ensure that they are 100% the same as on my develop computer. I've checked the file permissions on my computer and on the server computer. I am unable to run the RRD file as an administrator.

I've attached a copy of my RRD file.

Any ideas?

Thanks,

Ted Kitch
The administrator has disabled public write access.

Re:Failed to open the connection 28 Feb 2008 21:26 #115

  • tedkitch
  • tedkitch's Avatar
Didn't accept my upload. Here is the file.

Also, why does it say "Hacking Attempt" when you try to edit your message as suggested when you try to upload an invalid file type?

Thanks,

Ted

Attachment RRD.zip not found

Attachments:
The administrator has disabled public write access.

Re:Failed to open the connection 28 Feb 2008 21:40 #116

  • aellis
  • aellis's Avatar
Ted,

Which version of Progress are you running? I currently know of an incompatibility with the 9.X versions of Progress (and older) where you cannot use anything higher than Crystal 8.5 (this is a BusinessObjects limitation) and it effects Logicity as it is built on Crystal XI currently. The workaround is to stick with RPT Tool for Crystal 8.5 which is available in the "Old versions of Logicity" folder in the download area.

If you are on Progress 10.X, Logicity should work, but we may need to provide you with a registry patch.

Let me know,
Adam
The administrator has disabled public write access.

Re:Failed to open the connection 04 Jan 2012 22:30 #928

  • DavidBrown
  • DavidBrown's Avatar
  • Offline
Thanks for the quick resonse. I was able to pin the problem down to a bad ODBC setup. Recreated it and it works now. Thanks!
The administrator has disabled public write access.