Login to MS SQL server 7.0 1

[CestusGW]

To start, I've read through the documentation that Seagate gave out regarding problems with login looping - and my system has checked out As it stands right now, I have a .rpt on my CE 8.5 server that needs to connect to MS SQL server 7.0. However, I get the infamous "looping logon" problem. I have setup the system DSN on the server in a variety of ways, using NT auth, SQL auth, public accounts and private accounts. I have tested the reports from multiple machines using the exact same DSNs (even down to the dll version) with the same settings and have had no problems. An interesting point to note is that while looking at the logs for my SQL Server (I have full access to the SQL Server, CE server et al), tests from the ODBC setup screen got recorded as logins. Tests from the ODBC setup screen that failed showed as failed logins. However, no logs appear when I try and run the report off the web. Does anyone have any suggestions beyond what CR gives, or had a similar experience?

BTW, for those who read my previous thread, this is one of my attempts to solve my previous problems with the extra freedom my manager gave me

*this is the problem that does not end, yes it goes on and on my friend. some sucker, started coding it not knowing what it was, and hell continue coding it forever just because....*

 

[synapsevampire]

I'd try to simplify things as much as possible to help you isolate this:

Use a single table using the Native driver for SQL Server in a report and place that report into CE, making sure that you complete the database portion of CE when you bring the report in, then try to view it. (Native connectivity is faster anyway, but this is just for testing, you can return to your ODBC driver later).

If that doesn't cause the problem, you have a solid starting point upon which to explore. Now try creating a fresh CR ODBC connection which uses SQL Authorization, and use a God like privilege in SQL Server to avoid any problems. Remember to use Verify Database prior to saving reports, it tends to resolve connectivity issues.

-k

http://www.informeddatadecisions.com

kai@informeddatadecisions.com

 

[CestusGW]

Well, I've further isolated the problem - using a native connection actually throws me an honest to God error message. A native connection from my local machine to the SQL Server works just fine - when the report gets moved to the web it gives me a "Error detected by database DLL on [XXX.PageServer]" message, which tells me little. Even by going native, I haven't noticed any logon attempts through my SQL Server admin page. So there has to be something blocking CRE before it even tries. Does anyone know what this would be? Greg W
wolgemga@aecl.ca

 

[lyanch]

I have this problem with Oracle and My CE server... don't suppose your web server is a BDC?

Lisa

 

[CestusGW]

The Web Server is IIS 4.0 (not sure what a BDC is) running on NT 4.0 Server edition.
BDC = Big Dumb Computer?
Greg W
wolgemga@aecl.ca

 

[lyanch]

BDC = Backup Domain Controller

 

[synapsevampire]

Are all of your services working on the CE system?

Can you run the sample reports on the CE system?

Did you do a complete install of the CE system?

That error is VERY generic, I get it when the page server stops, and I get it when there's bad SQL (I use SQL Expressions).

If you get it just using a straight select from one table in a report, I'd guess that the problem is related to

-a service not working
or
-Connectivity not installed or incorrect
or
-Perhaps a threshold is exceeded (a timeout occurs and there are also row limitations in CE, the default is 20,000 I think, the error should be different though)

-k

http://www.informeddatadecisions.com

kai@informeddatadecisions.com

 

[synapsevampire]

Also, Lisa offers this up for a similar problem:

lyanch (Programmer) Jul 17, 2002
Running in console mode is essentially running the pageserver as an application from a dos prompt. (Just copy the execution line from the CMC, change -service to -console and run from a dos prompt.)

The pageserver was not intended to run as a process, but is designed to run as a service. It generally is not as stable, and often requests a second logon from my users.

Here is a link to a whitepaper on this problem.. didn't help me but you never know..

http://support.crystaldecisions.com/communityCS/TechnicalPapers/cr_error_detected_by_db_dll.pdf

Lisa

http://www.informeddatadecisions.com

kai@informeddatadecisions.com

 

[CestusGW]

The server is working perfectly, we've used very complex reports on it through a variety of databases - it's only SQL Server that has given us a problem. I agree that error message is quite generic. According to Seagate (in one of their documents), this error is returned when the DLL returns an error. It would be nice if Seagate had returned us the DLL error message with the generic message.
All the components are on a single server, and they are all working fine. The report is one field (a length 10 string) from one table in one database, only 50000 records. Upon reading in Seagates documentation, it was stated that the PageServer should be started in console mode when the registry keys for the database client where in HKEY_CURRENT_USER, not HKEY_LOCAL_MACHINE. Our database client keys are all located in HKEY_LOCAL_MACHINE, but after reading some other posts I think the console PageServer solution may work, despite the fact it appears to fix a problem my server doesnt have. Greg W
wolgemga@aecl.ca

 

[lyanch]

I get the error, but it isn't an error from the dll.. it never gets there. the APS itself creates the error. It is a permissions problem, but in my case it has to do with the way it asks for permissions from the oracle client.. the client refuses. I too run reports from other servers with no problem. This just started with Oracle, next week i start with SQL server, so we shall see.

Lisa

 

[CestusGW]

OK ... how is PageServer.exe supposed to work? On my system we stopped the pageserver service and then went to the console to try and make the pageserver a foreground application. After starting the pageserver we got error messages about how some values were already initialized and a cursor start point saying "@ your command:" The help from within the console yielded little help, and while we had this console open all our reports stopped working, stating that the pageserver was down. Where has Seagate stashed their documentation on how to use the pageserver.exe program in console mode? Has anybody else had similar results when running the pageserver.exe program like this? Greg W
wolgemga@aecl.ca

 

[synapsevampire]

Try scheduling the report, if it doesn't fail, then it may be the number of rows being returned, as I mentioned earlier, there is a limitation of 20,000 (you can set this).

http://support.crystaldecisions.com/library/kbase/articles/c2010988.asp

-k

http://www.informeddatadecisions.com

kai@informeddatadecisions.com

 

[CestusGW]

In the end it turned out that the CR documentation on using PageServer.exe was incorrect. I used Lisa's example and got a few error messages, but stuff started working \o/ The only problem with this is that it means someone has to be logged on to our server at all times now, which doesn't happen usually. Is there any way of starting the PageServer in console mode w/out a login, or is that integral to starting in console mode? Greg W
wolgemga@aecl.ca

 

[lyanch]

Pretty much one of the reasons that you don't want to use Console mode.

 

[synapsevampire]

The upside is that you know that it works, you now need to work out why the service is causing you headaches.

I occasionally have problems with the Page Server, more so when I used CE8.0, at worst case a reboot straightened it out.

There are a few settings available for the Page Server, some from within CMC, and some command line settings (use the Crystal Configuration Manager to add command line settings).

-k

http://www.informeddatadecisions.com

kai@informeddatadecisions.com