Intermittent data source problem - trying to access a deleted data source

Hello
I am using Reporting Services within Visual Studio .Net 2003, connecting to
a SQL Server 2000 database.
I am having an intermittent problem with a report misbehaving. The report
has 5 subreports, all of which work fine on their own (for the most part).
The problem is that, sometimes, when I run the main report I get the
following error:-
"An error occurred while executing the subreport ¡OppsHotProspects¢: An
error has occurred during report processing.
Cannot create a connection to data source 'GuessDB'."
This error sometimes only appears for one report, sometimes for all. The
issue is that the 'GuessDB' data source is no longer used; in its place the
'GuessDBLive' data source is now used. I have removed the 'GuessDB' data
source.
When I run each subreport by itself they run fine, and the data source used
in both the Data tab and the Preview tab is the correct one. One
subreport, however, intermittently misbehaves and gives the same error on
its own.
I am very confused as to why this is happening. Presumably something in
each subreport is referencing the deleted data source, but I can't figure
it out. The deleted one should not be getting used at all.
I'd appreciate any help!
Thanks
DeniseFor anyone else having the same problem, I think I've found the answer.
Out of sheer frustration, I examined the code on each report, and on one
there was a chunk of code which referenced the obsolete data source. I've
no idea why this code remained on one report and not the others, but it
did. I removed the offending code, and the problem (touch wood!) has been
resolved.
On Thu, 3 Nov 2005 12:03:38 +0000, Denise wrote:
> Hello
> I am using Reporting Services within Visual Studio .Net 2003, connecting to
> a SQL Server 2000 database.
> I am having an intermittent problem with a report misbehaving. The report
> has 5 subreports, all of which work fine on their own (for the most part).
> The problem is that, sometimes, when I run the main report I get the
> following error:-
> "An error occurred while executing the subreport ¡OppsHotProspects¢: An
> error has occurred during report processing.
> Cannot create a connection to data source 'GuessDB'."
> This error sometimes only appears for one report, sometimes for all. The
> issue is that the 'GuessDB' data source is no longer used; in its place the
> 'GuessDBLive' data source is now used. I have removed the 'GuessDB' data
> source.
> When I run each subreport by itself they run fine, and the data source used
> in both the Data tab and the Preview tab is the correct one. One
> subreport, however, intermittently misbehaves and gives the same error on
> its own.
> I am very confused as to why this is happening. Presumably something in
> each subreport is referencing the deleted data source, but I can't figure
> it out. The deleted one should not be getting used at all.
> I'd appreciate any help!
> Thanks
> Denise

Intermittent Connectivity issues though network is fine

Hi,

I am getting intermittent connectivity issues while connecting to a remote SQL Server 2000 database through the Enterprise Manager. It gives a time-out error

Initially I guessed it must be the network but then I was able to term-serv successfully into the remote server and work without any connectivity issues.

Any pointers how this is possible ?

Thanks for your help.

Regards,
-Ranjit S Hans.i think you have problem with the logging in.

to test this try to connect to this server using SQL Query analyzer and see if it gets connected instantly. If it's the case, there is something about the SQL Login you are using in app.

Hope this helps|||Thanks Wash. I had checked with my logins and they are fine. Also I dont see any issues with the server alias.

I have been thinking of increasing the timeout interval for the remote server.
Am wary to do it as it would need a restart of SQl services.

Any suggestions/workaround ?

Thanks,
-Ranjit

Intermittent connection dramas: "Cannot open user default database..."

Hi,
I've been experiencing some very strange, intermittent failures connecting
to an MS SQL database... basically at seemingly random times the server
decides that it can't open the requested database (reporting error 4062:
"Cannot open user default database. Using master database instead"). I've
so far been unable to track down any useful background to this error
message; has anyone on this group come across similar problems? Any clues
as to what might be triggering this sort of fault? More specific details
follow:
* In the majority of cases, connection is established correctly (albeit
sometimes a little slowly).
* Connections are being made to the local machine, using straightforward,
static code. The problem isn't something trivial like a mis-typed
database name, incorrect password etc. Re-running the SAME CODE will
eventually succeed.
* The server isn't particularly heavily loaded, and I can perceive no
pattern to the fault (it seems no more prevalent when the
server's busy, nor after any particular events).
* Nothing relevant is documented in the Event Viewer, nor the server logs.
Am I looking in the right place'
* We're running SQL Server 2005 Express Edition, latest service pack...
are there any connection rate limitations on this software? All
documentation I've seen indicates that there are not, but this behaviour
almost suggests that there may be...
* Connecting (from local machine) using PHP mssql module (latest stable
version).
* Although possibly symptomatic of a DoS, there's no other evidence to
suggest that this is the case (TCP to the service is firewalled).
Would be grateful for any advice on this issue.
Cheers,
Alex.HI Alex
Have you checked for Anti-virus or intrusion detection software in the
server, this can cause connections to fail. If you have the autoclose option
set for the database or attaching the database when you connect then if the
AV software is scanning the files you will not be able to do this.
You may also want to eliminate any particular machine or see if this occurs
on the server, to rule out general networking issues. Check firewalls are
correctly configured and if you are using group policies that they are not
interfering.
You may also want to check if you are service packed to a recent version.
John
"Alex Craven" wrote:
> Hi,
> I've been experiencing some very strange, intermittent failures connecting
> to an MS SQL database... basically at seemingly random times the server
> decides that it can't open the requested database (reporting error 4062:
> "Cannot open user default database. Using master database instead"). I've
> so far been unable to track down any useful background to this error
> message; has anyone on this group come across similar problems? Any clues
> as to what might be triggering this sort of fault? More specific details
> follow:
> * In the majority of cases, connection is established correctly (albeit
> sometimes a little slowly).
> * Connections are being made to the local machine, using straightforward,
> static code. The problem isn't something trivial like a mis-typed
> database name, incorrect password etc. Re-running the SAME CODE will
> eventually succeed.
> * The server isn't particularly heavily loaded, and I can perceive no
> pattern to the fault (it seems no more prevalent when the
> server's busy, nor after any particular events).
> * Nothing relevant is documented in the Event Viewer, nor the server logs.
> Am I looking in the right place'
> * We're running SQL Server 2005 Express Edition, latest service pack...
> are there any connection rate limitations on this software? All
> documentation I've seen indicates that there are not, but this behaviour
> almost suggests that there may be...
> * Connecting (from local machine) using PHP mssql module (latest stable
> version).
> * Although possibly symptomatic of a DoS, there's no other evidence to
> suggest that this is the case (TCP to the service is firewalled).
>
> Would be grateful for any advice on this issue.
> Cheers,
> Alex.
>
>|||Alex Craven wrote:
> Hi,
> I've been experiencing some very strange, intermittent failures connecting
> to an MS SQL database... basically at seemingly random times the server
> decides that it can't open the requested database (reporting error 4062:
> "Cannot open user default database. Using master database instead"). I've
> so far been unable to track down any useful background to this error
> message; has anyone on this group come across similar problems? Any clues
> as to what might be triggering this sort of fault? More specific details
> follow:
> * In the majority of cases, connection is established correctly (albeit
> sometimes a little slowly).
> * Connections are being made to the local machine, using straightforward,
> static code. The problem isn't something trivial like a mis-typed
> database name, incorrect password etc. Re-running the SAME CODE will
> eventually succeed.
> * The server isn't particularly heavily loaded, and I can perceive no
> pattern to the fault (it seems no more prevalent when the
> server's busy, nor after any particular events).
> * Nothing relevant is documented in the Event Viewer, nor the server logs.
> Am I looking in the right place'
> * We're running SQL Server 2005 Express Edition, latest service pack...
> are there any connection rate limitations on this software? All
> documentation I've seen indicates that there are not, but this behaviour
> almost suggests that there may be...
> * Connecting (from local machine) using PHP mssql module (latest stable
> version).
> * Although possibly symptomatic of a DoS, there's no other evidence to
> suggest that this is the case (TCP to the service is firewalled).
>
> Would be grateful for any advice on this issue.
> Cheers,
> Alex.
>
>
Make sure the "problem" database isn't configured for auto-close, also
make sure it's not the target for log-shipping, or some other process
that might take it offline to do a restore, etc.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Do you periodically rename, remove, or detach the database?
Do you have any jobs that put the database into single-user mode or
otherwise alter the availability of the database?|||On Fri, 29 Sep 2006 08:14:30 -0500, Tracy McKibben uttered:
[...]
> Make sure the "problem" database isn't configured for auto-close, also
> make sure it's not the target for log-shipping, or some other process
> that might take it offline to do a restore, etc.
Hi Tracy et al,
Thanks for all your advice; so far it looks like the auto-close 'feature'
was most likely the root of my problems (or at least a major factor...);
the system seems to be performing rather more reliably with that disabled.
Cheers,
Alex.|||Alex Craven wrote:
> On Fri, 29 Sep 2006 08:14:30 -0500, Tracy McKibben uttered:
> [...]
>> Make sure the "problem" database isn't configured for auto-close, also
>> make sure it's not the target for log-shipping, or some other process
>> that might take it offline to do a restore, etc.
>
> Hi Tracy et al,
> Thanks for all your advice; so far it looks like the auto-close 'feature'
> was most likely the root of my problems (or at least a major factor...);
> the system seems to be performing rather more reliably with that disabled.
> Cheers,
> Alex.
>
That auto-close option should NEVER be enabled for a production
database. Another one to watch out for is auto-shrink.
Tracy McKibben
MCDBA
http://www.realsqlguy.com

Intermittent access to SQL Server 2005

I'm having weird issues with connecting to MS SQL Server. Sometimes it can establish a connection and sometimes it can't. This is both with ODBC and with .net code. This happens on multiple computers. I.e. one minute you can connect, the next you can't.

I have a SQL 2000 server which connects fine every time. So I assume the problem is with the upgraded MS SQL Server. I want to be able to resolve this issue before upgrading the main server to SQL 2005.

Seems it was either a Service Pack issue, (installed SP2) or an IP subnet mask issue. But it's working now.|||Mark answerred. Please post more detailed info (error message) here if the issue comes up again.

Interesting issue connecting to Sql server through a firewall..

We have an app in development. The front end of the app is web-based running
tomcat.
This app sits in our DMZ.
This app communicates to a sql 2000 server on our corporate network. The
connection is via microsofts jdbc 2000 connector.
We have allowed the server hosting the app to initiate connections to the
internal sql server on port 1433 only. The sql server can communicat any/any
back to the dmz.
I am seeing some interesting behavior - The front end initiates a connection
to the DB server on 1433 which is successful, but then also tries to
initiate a connection on 137 (named pipes/nbname), of course the firewall
blocks this and it eventually times out. and the opens addtional pool
connection on 1433. This causes the app to load very slowly as the pages
are data driven. If we open up 137 then the app runs at a normal speed.
I dont understant why the front end is trying to communicate to the server
on anything other than 1433. The server is configured for tcp/ip only. The
JDBC driver and app on the front end is doing everything by IP address.
I've thought of trying a host file on the front end resolving the back end.
and vice versa, but this shouldnt matter as everything is IP and not name.
I am now trying to figure out if this is an issue with the microsoft jdbc
driver config - though it looks like you dont have the ability to specify
protocols in it, an issue witht he sql server - perhaps the response to the
initial connection is telling the client to talk named pipes, or if its
just an OS issue.
Leaving 137 open from the dmz app to the internal sql server is not an
option.
Thanks in advance.
BillConnecting with an IP address doesn't necessarily mean that
the clients will use TCP/IP for the network library. Try to
force the clients to connect through TCP/IP by specifying
the network library to use, e.g.
Network Library=DBMSSOCN
I don't know about the issue with specifying libraries with
the JDBC driver but you can also set this up on the client
by configuring an alias and the network library with the
Client Network Utility.
-Sue
On Tue, 30 Mar 2004 16:22:15 -0600, "Bill B"
<fakexxbbaulingyy@.unitedcenter.com> wrote:

>We have an app in development. The front end of the app is web-based runnin
g
>tomcat.
>This app sits in our DMZ.
>This app communicates to a sql 2000 server on our corporate network. The
>connection is via microsofts jdbc 2000 connector.
>We have allowed the server hosting the app to initiate connections to the
>internal sql server on port 1433 only. The sql server can communicat any/an
y
>back to the dmz.
>I am seeing some interesting behavior - The front end initiates a connectio
n
>to the DB server on 1433 which is successful, but then also tries to
>initiate a connection on 137 (named pipes/nbname), of course the firewall
>blocks this and it eventually times out. and the opens addtional pool
>connection on 1433. This causes the app to load very slowly as the pages
>are data driven. If we open up 137 then the app runs at a normal speed.
>I dont understant why the front end is trying to communicate to the server
>on anything other than 1433. The server is configured for tcp/ip only. The
>JDBC driver and app on the front end is doing everything by IP address.
>I've thought of trying a host file on the front end resolving the back end.
>and vice versa, but this shouldnt matter as everything is IP and not name.
>I am now trying to figure out if this is an issue with the microsoft jdbc
>driver config - though it looks like you dont have the ability to specify
>protocols in it, an issue witht he sql server - perhaps the response to the
>initial connection is telling the client to talk named pipes, or if its
>just an OS issue.
>Leaving 137 open from the dmz app to the internal sql server is not an
>option.
>Thanks in advance.
>Bill
>
>
>|||Hi Bill,
The Microsoft JDBC Driver will only work with TCP. Named pipe
connections would use 139 or 445, not 137.
Are you running Microsoft Enterprise Manager on the same network or are you
only running the JDBC app from the machine?
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

interesting connection problem

I am having a problem connecting with SQL server management . I get the error I have posted at the end of the message. However, I can successfully connect with my application. I use the same connection attributes with no success. Same login, same protocol, from the same machine.

Any Ideas?

Thanks!

Tracy

TITLE: Connect to Server

Cannot connect to DEEPSHEEP\SQLEXPRESS.

ADDITIONAL INFORMATION:

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=-1&LinkId=20476

BUTTONS:

OK

Can you connect to the instance locally by using ".\SQLEXPRESS" instead of "DEEPSHEEP\SQLEXPRESS"?

Do you have SP1 installed with the SSMS Express Edition management tools?

Paul A. Mestemaker II
Program Manager
Microsoft SQL Server
http://blogs.msdn.com/sqlrem/

Integrity Server Connecting to SQL Server

Installing Integrity Server on MS Server 2003 but having problems when Specifing the Database, prior to this install i've already installed JDBC driver on this server version 3.
At this stage of install of the Integrity Server its trying to connect to the SQL Server (SQL Enterprise Manager V8 with SP3 on MS Server 2003)which is sitting in the same Domain. An Error appears
" A problem was encountered when trying to connect to the database JDBC.
[Microsoft][SQL Server 2000 driver for JDBC][SQL Server]Login failled
for user SA, Reason: Not associated with a trusted SQL Server
connection"
Can please help
*****************************************
* This message was posted via http://www.sqlmonster.com
*
* Report spam or abuse by clicking the following URL:
* http://www.sqlmonster.com/Uwe/Abuse...4603ecbf9ea539
*****************************************
The error message indicates you are trying to connect to SQL
Server using SQL authentication and a SQL Server login.
However, your SQL Server is configured for Windows
Authentication only. It's not a good idea to use sa but if
that's what is required you need to change SQL Server to use
both Windows and SQL Server authentication.
-Sue
On Wed, 10 Nov 2004 16:14:23 GMT, "jaimoon patel via
SQLMonster.com" <forum@.SQLMonster.com> wrote:

>Installing Integrity Server on MS Server 2003 but having problems when Specifing the Database, prior to this install i've already installed JDBC driver on this server version 3.
>At this stage of install of the Integrity Server its trying to connect to the SQL Server (SQL Enterprise Manager V8 with SP3 on MS Server 2003)which is sitting in the same Domain. An Error appears
>" A problem was encountered when trying to connect to the database JDBC.
> [Microsoft][SQL Server 2000 driver for JDBC][SQL Server]Login failled
> for user SA, Reason: Not associated with a trusted SQL Server
> connection"
>Can please help
>*****************************************
>* This message was posted via http://www.sqlmonster.com
>*
>* Report spam or abuse by clicking the following URL:
>* http://www.sqlmonster.com/Uwe/Abuse...4603ecbf9ea539
>*****************************************

Integrity Server Connecting to SQL Server

Installing Integrity Server on MS Server 2003 but having problems when Speci
fing the Database, prior to this install i've already installed JDBC driver
on this server version 3.
At this stage of install of the Integrity Server its trying to connect to th
e SQL Server (SQL Enterprise Manager V8 with SP3 on MS Server 2003)which is
sitting in the same Domain. An Error appears
" A problem was encountered when trying to connect to the database JDBC.
[Microsoft][SQL Server 2000 driver for JDBC][SQL Server]Login fa
illed
for user SA, Reason: Not associated with a trusted SQL Server
connection"
Can please help
****************************************
*
* This message was posted via http://www.droptable.com
*
* Report spam or abuse by clicking the following URL:
* [url]http://www.droptable.com/Uwe/Abuse.aspx?aid=87f62ecdc6c849cbbf4603ecbf9ea539[/u
rl]
****************************************
*The error message indicates you are trying to connect to SQL
Server using SQL authentication and a SQL Server login.
However, your SQL Server is configured for Windows
Authentication only. It's not a good idea to use sa but if
that's what is required you need to change SQL Server to use
both Windows and SQL Server authentication.
-Sue
On Wed, 10 Nov 2004 16:14:23 GMT, "jaimoon patel via
droptable.com" <forum@.droptable.com> wrote:

>Installing Integrity Server on MS Server 2003 but having problems when Spec
ifing the Database, prior to this install i've already installed JDBC driver
on this server version 3.
>At this stage of install of the Integrity Server its trying to connect to t
he SQL Server (SQL Enterprise Manager V8 with SP3 on MS Server 2003)which is
sitting in the same Domain. An Error appears
>" A problem was encountered when trying to connect to the database JDBC.
> [Microsoft][SQL Server 2000 driver for JDBC][SQL Server]Login
failled
> for user SA, Reason: Not associated with a trusted SQL Server
> connection"
>Can please help
> ****************************************
*
>* This message was posted via http://www.droptable.com
>*
>* Report spam or abuse by clicking the following URL:
>* [url]http://www.droptable.com/Uwe/Abuse.aspx?aid=87f62ecdc6c849cbbf4603ecbf9ea539[/
url]
> ****************************************
*

Integrity Server Connecting to SQL Server

Installing Integrity Server on MS Server 2003 but having problems when Specifing the Database, prior to this install i've already installed JDBC driver on this server version 3.
At this stage of install of the Integrity Server its trying to connect to the SQL Server (SQL Enterprise Manager V8 with SP3 on MS Server 2003)which is sitting in the same Domain. An Error appears
" A problem was encountered when trying to connect to the database JDBC.
[Microsoft][SQL Server 2000 driver for JDBC][SQL Server]Login failled
for user SA, Reason: Not associated with a trusted SQL Server
connection"
Can please help
*****************************************
* This message was posted via http://www.sqlmonster.com
*
* Report spam or abuse by clicking the following URL:
* http://www.sqlmonster.com/Uwe/Abuse.aspx?aid=87f62ecdc6c849cbbf4603ecbf9ea539
*****************************************The error message indicates you are trying to connect to SQL
Server using SQL authentication and a SQL Server login.
However, your SQL Server is configured for Windows
Authentication only. It's not a good idea to use sa but if
that's what is required you need to change SQL Server to use
both Windows and SQL Server authentication.
-Sue
On Wed, 10 Nov 2004 16:14:23 GMT, "jaimoon patel via
SQLMonster.com" <forum@.SQLMonster.com> wrote:
>Installing Integrity Server on MS Server 2003 but having problems when Specifing the Database, prior to this install i've already installed JDBC driver on this server version 3.
>At this stage of install of the Integrity Server its trying to connect to the SQL Server (SQL Enterprise Manager V8 with SP3 on MS Server 2003)which is sitting in the same Domain. An Error appears
>" A problem was encountered when trying to connect to the database JDBC.
> [Microsoft][SQL Server 2000 driver for JDBC][SQL Server]Login failled
> for user SA, Reason: Not associated with a trusted SQL Server
> connection"
>Can please help
>*****************************************
>* This message was posted via http://www.sqlmonster.com
>*
>* Report spam or abuse by clicking the following URL:
>* http://www.sqlmonster.com/Uwe/Abuse.aspx?aid=87f62ecdc6c849cbbf4603ecbf9ea539
>*****************************************