Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

DSN not connecting to server

Status
Not open for further replies.

andie18

MIS
Aug 14, 2001
198
US
Hello,

I have written a report using CR 8.5 developer. It is suppose to log into a GoldMine database on a Windows 2003 standard server. The GoldMine backend is SQL 2000. I have setup a file .dsn for the report. It is not a complicated report either. I have 3 parameters on the report. 1 is a beging date, one is an end date and the third is to select multiple sales reps. I am getting ODBC errors on both the local workstations where I installed the distribution kit as well as the designer (which I run thru a VPN connection) The error is the standard cannot log in. This is an intermitten problem too to make matters worse. They also use a faxing program that gives errors stating that it cannot find GoldMine on the server. These errors are also intermitten. Both of these errors happen a quite a few times a day. After you click on the error enough times, the report and faxing program run just fine.

I ran this report on another network thru the designer and a different VPN connection and it seems totally fine so I do not think that it is necessarily the report. I am wondering if the network admin missed some sort of setting on the server. He has been monitoring the network traffic for the past few days it is seems clean to him.

any ideas?
 
let me add one other thing to this.

On both the workstations and the designer, if the report does run and you select several users, you cannot export it on the first try. Crystal crashes (crw32.exe). It is not so much as the multiple users as the amount of data. I can have the same issue with 2 users and a large amount of data.

I believe that when the report was first installed, it seemed to have printed just fine for about 2 weeks. Now that might be a coincedence with the data size. But the ODBC did not fail in that timeframe
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top