VB Crystal Report, Server Has not yet been opened Error with Crystal Reports 7

Server Has not yet been opened Error with Crystal Reports 7

Author	Message
Joe #1 / 4	Server Has not yet been opened Error with Crystal Reports 7 Hi to all. I'm finding many problems with a VB6 application I am mantaining. This application uses 4 reports: 2 of them are developed using Crystal Reports 7, while the other were developed using the internal VB Crystal Report Editor. THe application, and so the reports obviously, connects to a remote SQL Server (6.5 I think) database, protected by a firewall. Users encounter problems (the famous "Server Has not yet been opened" error) when trying to execute one of the two reports developed in Crystal Reports. I'm not sure, but i think that this problem began when users migrated from Windows NT to Windows XP. I don't think it's an XP problem, as I tested the application on its test environment (a Sql Server 7 Database, remote but NOT protected by a firewall), and ALL the reports worked properly. Someone has ideas about all this mess? Some friends told me that perhaps is a protocol problem (perhaps the firewall accepts only requests via TCP/IP and the database or the reports go via Named Pipes). Thanks JoeC
Sat, 12 Mar 2005 16:30:25 GMT

CW #2 / 4	Server Has not yet been opened Error with Crystal Reports 7 How does your reports designed using CR 7 connect to the server? ODBC? OLE DB? ADO? If you can run reports created inside VB, then there is no reason why reports created in CR 7 can't run. In fact, I never create reports inside VB using the CR designer due to its lack of flexibility. I suspect it's more likely to be due to authentication issue. Quote: > Hi to all. > I'm finding many problems with a VB6 application I am mantaining. This > application uses 4 reports: 2 of them are developed using Crystal > Reports 7, while the other were developed using the internal VB > Crystal Report Editor. > THe application, and so the reports obviously, connects to a remote > SQL Server (6.5 I think) database, protected by a firewall. > Users encounter problems (the famous "Server Has not yet been opened" > error) when trying to execute one of the two reports developed in > Crystal Reports. > I'm not sure, but i think that this problem began when users migrated > from Windows NT to Windows XP. I don't think it's an XP problem, as I > tested the application on its test environment (a Sql Server 7 > Database, remote but NOT protected by a firewall), and ALL the reports > worked properly. > Someone has ideas about all this mess? Some friends told me that > perhaps is a protocol problem (perhaps the firewall accepts only > requests via TCP/IP and the database or the reports go via Named > Pipes). > Thanks > JoeC
Sat, 12 Mar 2005 20:44:55 GMT

Arnaldo Martine #3 / 4	Server Has not yet been opened Error with Crystal Reports 7 Dear Joe: Try to use this line of code on the form where the CRViewer is call from (on every form). Put the line of code above the CRViewer code that is there within the form code (see below). Replace the 4 variables with yours. (Line of Code) Report.Database.Tables.Item(1).SetLogOnInfo Trim(servername), "databasename", Trim(UserID), Trim(pwdID) (Sample Code) Private Sub Form_Load() ' Report.Database.Tables.Item(1).SetLogOnInfo Trim(servername), "databasename", Trim(UserID), Trim(pwdID) Screen.MousePointer = vbHourglass CRViewer1.ReportSource = Report CRViewer1.ViewReport Screen.MousePointer = vbDefault End Sub arnnie Quote: > Hi to all. > I'm finding many problems with a VB6 application I am mantaining. This > application uses 4 reports: 2 of them are developed using Crystal > Reports 7, while the other were developed using the internal VB > Crystal Report Editor. > THe application, and so the reports obviously, connects to a remote > SQL Server (6.5 I think) database, protected by a firewall. > Users encounter problems (the famous "Server Has not yet been opened" > error) when trying to execute one of the two reports developed in > Crystal Reports. > I'm not sure, but i think that this problem began when users migrated > from Windows NT to Windows XP. I don't think it's an XP problem, as I > tested the application on its test environment (a Sql Server 7 > Database, remote but NOT protected by a firewall), and ALL the reports > worked properly. > Someone has ideas about all this mess? Some friends told me that > perhaps is a protocol problem (perhaps the firewall accepts only > requests via TCP/IP and the database or the reports go via Named > Pipes). > Thanks > JoeC
Sat, 12 Mar 2005 22:23:17 GMT

Arnaldo Martine #4 / 4	Server Has not yet been opened Error with Crystal Reports 7 Dear Joe: Try to use this line of code on the form where the CRViewer is call from (on every form). Put the line of code above the CRViewer code that is there within the form code (see below). Replace the 4 variables with yours. (Line of Code) Report.Database.Tables.Item(1).SetLogOnInfo Trim(servername), "databasename", Trim(UserID), Trim(pwdID) (Sample Code) Private Sub Form_Load() ' Report.Database.Tables.Item(1).SetLogOnInfo Trim(servername), "databasename", Trim(UserID), Trim(pwdID) Screen.MousePointer = vbHourglass CRViewer1.ReportSource = Report CRViewer1.ViewReport Screen.MousePointer = vbDefault End Sub arnnie Quote: > Hi to all. > I'm finding many problems with a VB6 application I am mantaining. This > application uses 4 reports: 2 of them are developed using Crystal > Reports 7, while the other were developed using the internal VB > Crystal Report Editor. > THe application, and so the reports obviously, connects to a remote > SQL Server (6.5 I think) database, protected by a firewall. > Users encounter problems (the famous "Server Has not yet been opened" > error) when trying to execute one of the two reports developed in > Crystal Reports. > I'm not sure, but i think that this problem began when users migrated > from Windows NT to Windows XP. I don't think it's an XP problem, as I > tested the application on its test environment (a Sql Server 7 > Database, remote but NOT protected by a firewall), and ALL the reports > worked properly. > Someone has ideas about all this mess? Some friends told me that > perhaps is a protocol problem (perhaps the firewall accepts only > requests via TCP/IP and the database or the reports go via Named > Pipes). > Thanks > JoeC
Sat, 12 Mar 2005 22:22:57 GMT

Page 1 of 1

[ 4 post ]