stealthtron
Programmer
"DBProcess is dead or not enabled." - Anyone here who has an idea what exactly is causing this in Crystal Reports? (Btw, I'm using CR v8.5)
Thank you in advance.
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 Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Crystal Reports: Database Error
- Thread starter stealthtron
- Start date
- Status
"DBProcess is dead or not enabled." - Anyone here who has an idea what exactly is causing this in Crystal Reports? (Btw, I'm using CR v8.5)
Thank you in advance.
Hi,
I copied and pasted your error in Google, did a search and came up with one of many sources of explanation. The following may offer some insight.
Go to page 163 of the following pdf for an explanation, and page 164 for the resolutions.
Q
I copied and pasted your error in Google, did a search and came up with one of many sources of explanation. The following may offer some insight.
Go to page 163 of the following pdf for an explanation, and page 164 for the resolutions.
Q
- Thread starter
- #3
stealthtron
Programmer
Hi Qu1ncy,
Cool! Thanks for the effort in paving for a good insight on what's causing the prob--which has something to do with a no. of factors that aborts a SQL connection for a return set back to a requesting client.
The documentation pointed out in page 163 has been very helpful, with similar terms used in that of MS SQL Server's-- where my CR report connects to--(which is not surprising as it had its roots from Sybase SQL Server). Thank you.
I'm left with still one issue though:
At the time I received the "DBProcess is dead or not enabled" runtime msg in Crystal, I tried refreshing SQL Analyzer for the report's same underlying stored procedure; and, as opposed to what was expected, I was able to connect. Hmmm... strange!? (just my curiosity ;-))
Tnx again.
Cool! Thanks for the effort in paving for a good insight on what's causing the prob--which has something to do with a no. of factors that aborts a SQL connection for a return set back to a requesting client.
The documentation pointed out in page 163 has been very helpful, with similar terms used in that of MS SQL Server's-- where my CR report connects to--(which is not surprising as it had its roots from Sybase SQL Server). Thank you.
I'm left with still one issue though:
At the time I received the "DBProcess is dead or not enabled" runtime msg in Crystal, I tried refreshing SQL Analyzer for the report's same underlying stored procedure; and, as opposed to what was expected, I was able to connect. Hmmm... strange!? (just my curiosity ;-))
Tnx again.
- Status
Similar threads
- Locked
- Question
- Locked
- Question