cannot open sql server, stored procedures on web

[Tracey]

Hi

I have created a relatively simple report based on a stored procedure in my IB6 Db.

This report seems to be triggering an error in the page server. On occasion (not every time) when accessing this report, the user is greeted with:

"Cannot open sql server [on pageserver servername.pageserver]"

This is remedied (until next time) by re-starting the pageserver, and has (today) happened 5 times in 2 hours while the report was being accessed regularly.

Are there any known issues with stored procedures over the web? I am using stored procedures because of the documented instability of sql based reports on the web.

I have applied ALL patches, and in general my services restarts are kept to a minimum these days. (despite being fobbed off by seagate because i use apache)

specs:
CR8.5
CE8 web components
Apache 2.036
Interbase 6
win2000 (server)

Has anyone had any RELEVANT experiences here they could share with me?

 

[jonwolds]

Hi,

I've just received the same message. I solved it by checking the permissions on the stored proc, and making sure i had read rights to all the tables being used.

Hope this helps.

Jon

 

[Tracey]

I am using the default user to log into firebird.. therefore have default permissions.

I have never ventured into this region, so dont know a lot about it.
I amin the db with IBAdmin, and have just now ventured into the grant manager.

are we talking the user's permissions or the object's permissions?

seems strange that it should let the report run sometimes and overcome the problem on restart of it is a permissions issue.

 

[Hypermommy]

Hi all,

I know this is an old thread but we're having the same error message except we're not using stored procedures. I've seen several mentions of the problem on here and google but no solution that's quite on for us yet. Basically, what happened is this -- old reports that have not been modified and new reports that I have modified recently (went into infostore, copied the a_042/232/000/40242/q012408.rpt [or whatever the numbering scheme is], modified it and then copied the q012408.rpt back out there overwriting what was there]) are now giving us problems.

I can't see how it would be related to the method of modifying the rpeort but maybe it is so I put this info in here. But if that were the case then why is it affecting reports that haven't been modified too?

I'm really stumped and don't know why we're getting this error. One other thing is that it doesn't seem to happen unless it's a report that requests a parameter.

Hope you guys can help .. sure appreciate your time and consideration regardless.

-= Hypermommy =-

 

[Tracey]

Yes you are right, an old post i can hardly remember it.

As far as I can recall, the problem just mysteriously stopped after the patching etc i did on my web server crystal components. (I checked my log and i have noted the problem, but no cure)

The good news is, i havent had to do a restart of my crystal web components all year.

Sorry I can be of more help. We had so many "mysterious" problems with Crystal that we have now phased it out in favour of HTML reports written in Delphi. Much more reliable and less complicated to develop.