Error accessing report: running

Showing posts with label running. Show all posts

Thursday, March 29, 2012

Error executing SSIS package

Hello,
I'm running SQL Server 2005 Developer edition on Vista Ultimate. I've
created several SSIS packages and run them under proxy account. At first
they worked just fine, but then all of them started to fail with the error
messages like this one:
Error: 2007-03-20 22:59:15.56 Code: 0xC002F304 Source:
NonTransactableSql Execute SQL Task Description: An error occurred with
the following error message: "Could not find file 'I:\Users\Peter
Afonin\AppData\Local\Temp\tmp458F.tmp'.". End Error DTExec: The package
execution returned DTSER_FAILURE (1). Started: 10:59:14 PM Finished:
10:59:15 PM Elapsed: 1.014 seconds. The package execution failed. The
step failed.
If the cause is really in this tmp file, it doesn't make any sense. Yes, I'm
deleting my tmp files periodically, so I don't have these files. It's hard
to believe that SQL Server relies on tmp files that are often deleted. Plus,
I was running the same packages on Windows XP for over a year and never had
problems like this.
What else could it be and how to fix it? Is it a security issue?
I would appreciate your suggestions very much.
Thank you,
--
Peter AfoninHi Peter
"Peter Afonin" wrote:
> Hello,
> I'm running SQL Server 2005 Developer edition on Vista Ultimate. I've
> created several SSIS packages and run them under proxy account. At first
> they worked just fine, but then all of them started to fail with the error
> messages like this one:
> Error: 2007-03-20 22:59:15.56 Code: 0xC002F304 Source:
> NonTransactableSql Execute SQL Task Description: An error occurred with
> the following error message: "Could not find file 'I:\Users\Peter
> Afonin\AppData\Local\Temp\tmp458F.tmp'.". End Error DTExec: The package
> execution returned DTSER_FAILURE (1). Started: 10:59:14 PM Finished:
> 10:59:15 PM Elapsed: 1.014 seconds. The package execution failed. The
> step failed.
> If the cause is really in this tmp file, it doesn't make any sense. Yes, I'm
> deleting my tmp files periodically, so I don't have these files. It's hard
> to believe that SQL Server relies on tmp files that are often deleted. Plus,
> I was running the same packages on Windows XP for over a year and never had
> problems like this.
> What else could it be and how to fix it? Is it a security issue?
> I would appreciate your suggestions very much.
> Thank you,
> --
> Peter Afonin
>
I would suspect that the issue is probably with 'I:\Users\Peter
Afonin\AppData\Local\Temp' not existing where is your temp directory set to?
John|||Hi John,
No, this directory is real. This is a default directory in Vista (I have it
on partition I).
Thank you,
Peter
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:6899EAEE-6306-4D47-913B-BF503C445D66@.microsoft.com...
> Hi Peter
> "Peter Afonin" wrote:
>> Hello,
>> I'm running SQL Server 2005 Developer edition on Vista Ultimate. I've
>> created several SSIS packages and run them under proxy account. At first
>> they worked just fine, but then all of them started to fail with the
>> error
>> messages like this one:
>> Error: 2007-03-20 22:59:15.56 Code: 0xC002F304 Source:
>> NonTransactableSql Execute SQL Task Description: An error occurred
>> with
>> the following error message: "Could not find file 'I:\Users\Peter
>> Afonin\AppData\Local\Temp\tmp458F.tmp'.". End Error DTExec: The package
>> execution returned DTSER_FAILURE (1). Started: 10:59:14 PM Finished:
>> 10:59:15 PM Elapsed: 1.014 seconds. The package execution failed. The
>> step failed.
>> If the cause is really in this tmp file, it doesn't make any sense. Yes,
>> I'm
>> deleting my tmp files periodically, so I don't have these files. It's
>> hard
>> to believe that SQL Server relies on tmp files that are often deleted.
>> Plus,
>> I was running the same packages on Windows XP for over a year and never
>> had
>> problems like this.
>> What else could it be and how to fix it? Is it a security issue?
>> I would appreciate your suggestions very much.
>> Thank you,
>> --
>> Peter Afonin
> I would suspect that the issue is probably with 'I:\Users\Peter
> Afonin\AppData\Local\Temp' not existing where is your temp directory set
> to?
> John|||John, I can confirm that SQL Server is indeed looking for these tmp files.
1. I've recreated my packages, they worked fine.
2. I removed all files from I:\Users\Peter Afonin\AppData\Local\Temp folder.
The packages stopped working, giving me the error I mentioned before.
3. I put these tmp files back to this folder, the packages work fine again.
This is something that I've never heard before and that doesn't make any
sense. Why this never happened on Windows XP, only Vista? What should I do -
it looks like I cannot cleanup my computer anymore?
As a last resort - can I change the folder for tmp files that are needed for
SSIS packages execution, so I could exclude it somehow from the disk
cleanup?
Any advice would be greatly appreciated.
Thank you,
Peter
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:6899EAEE-6306-4D47-913B-BF503C445D66@.microsoft.com...
> Hi Peter
> "Peter Afonin" wrote:
>> Hello,
>> I'm running SQL Server 2005 Developer edition on Vista Ultimate. I've
>> created several SSIS packages and run them under proxy account. At first
>> they worked just fine, but then all of them started to fail with the
>> error
>> messages like this one:
>> Error: 2007-03-20 22:59:15.56 Code: 0xC002F304 Source:
>> NonTransactableSql Execute SQL Task Description: An error occurred
>> with
>> the following error message: "Could not find file 'I:\Users\Peter
>> Afonin\AppData\Local\Temp\tmp458F.tmp'.". End Error DTExec: The package
>> execution returned DTSER_FAILURE (1). Started: 10:59:14 PM Finished:
>> 10:59:15 PM Elapsed: 1.014 seconds. The package execution failed. The
>> step failed.
>> If the cause is really in this tmp file, it doesn't make any sense. Yes,
>> I'm
>> deleting my tmp files periodically, so I don't have these files. It's
>> hard
>> to believe that SQL Server relies on tmp files that are often deleted.
>> Plus,
>> I was running the same packages on Windows XP for over a year and never
>> had
>> problems like this.
>> What else could it be and how to fix it? Is it a security issue?
>> I would appreciate your suggestions very much.
>> Thank you,
>> --
>> Peter Afonin
> I would suspect that the issue is probably with 'I:\Users\Peter
> Afonin\AppData\Local\Temp' not existing where is your temp directory set
> to?
> John|||Hi Peter
"Peter Afonin" wrote:
> John, I can confirm that SQL Server is indeed looking for these tmp files.
> 1. I've recreated my packages, they worked fine.
> 2. I removed all files from I:\Users\Peter Afonin\AppData\Local\Temp folder.
> The packages stopped working, giving me the error I mentioned before.
> 3. I put these tmp files back to this folder, the packages work fine again.
> This is something that I've never heard before and that doesn't make any
> sense. Why this never happened on Windows XP, only Vista? What should I do -
> it looks like I cannot cleanup my computer anymore?
> As a last resort - can I change the folder for tmp files that are needed for
> SSIS packages execution, so I could exclude it somehow from the disk
> cleanup?
> Any advice would be greatly appreciated.
> Thank you,
> Peter
>
SSIS may use files in a users temporary directory, if they have been
automatically generated or converted. You will need to check the datasources
and the package steps to see what they are. If necessary they can be moved to
a "common" directory that has the correct permissions for all users that will
run the package.
You may have found that removing the equivalent files in windows XP would
have had a similar result.
John|||Thank you, John, I'll edit my packages and see what's going on.
Peter
On Mar 22, 1:44 am, John Bell <jbellnewspo...@.hotmail.com> wrote:
> HiPeter
>
>
> "PeterAfonin" wrote:
> > John, I can confirm that SQL Server is indeed looking for these tmp files.
> > 1. I've recreated my packages, they worked fine.
> > 2. I removed all files from I:\Users\PeterAfonin\AppData\Local\Temp folder.
> > The packages stopped working, giving me the error I mentioned before.
> > 3. I put these tmp files back to this folder, the packages work fine again.
> > This is something that I've never heard before and that doesn't make any
> > sense. Why this never happened on Windows XP, only Vista? What should I do -
> > it looks like I cannot cleanup my computer anymore?
> > As a last resort - can I change the folder for tmp files that are needed for
> > SSIS packages execution, so I could exclude it somehow from the disk
> > cleanup?
> > Any advice would be greatly appreciated.
> > Thank you,
> >Peter
> SSIS may use files in a users temporary directory, if they have been
> automatically generated or converted. You will need to check the datasources
> and the package steps to see what they are. If necessary they can be moved to
> a "common" directory that has the correct permissions for all users that will
> run the package.
> You may have found that removing the equivalent files in windows XP would
> have had a similar result.
> John- Hide quoted text -
> - Show quoted text -

error executing query

I have a database running on MSDE it was working fine. Recently when I try t
o select from the database I am getting the following error after a few reco
rds have been returned. All of the tables are giving this problem. Not sure
what to do.
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForD
ata (CheckforData()).
[Microsoft][ODBC SQL Server Driver][DBNETLIB]General network err
or. Check your network documentation.
Connection Broken"Warren" <anonymous@.discussions.microsoft.com> wrote in message
news:E77B88A4-C231-4C30-B2D2-C4282A43A32F@.microsoft.com...
> I have a database running on MSDE it was working fine. Recently when I try
to select from the database I am getting the following error after a few
records have been returned. All of the tables are giving this problem. Not
sure what to do.
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData[/c
olor]
(CheckforData()).
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]General network error. Ch
eck
your network documentation.
> Connection Broken
>
It could be several things... first a question: were any changes made or
different software installed on the computer running MSDE?
If not, databases like MSDE and SQL Server can expose network issues such as
packet drops or interruptions. Also, rule out name resolution problems like
DNS or WINS.
Another angle, consider installing the latest version of MDAC on the client
computer and enabling both SQL Server utilities TCP/IP and Named Pipes.
Steve

error executing query

I have a database running on MSDE it was working fine. Recently when I try to select from the database I am getting the following error after a few records have been returned. All of the tables are giving this problem. Not sure what to do.
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData (CheckforData()).
[Microsoft][ODBC SQL Server Driver][DBNETLIB]General network error. Check your network documentation.
Connection Broken
"Warren" <anonymous@.discussions.microsoft.com> wrote in message
news:E77B88A4-C231-4C30-B2D2-C4282A43A32F@.microsoft.com...
> I have a database running on MSDE it was working fine. Recently when I try
to select from the database I am getting the following error after a few
records have been returned. All of the tables are giving this problem. Not
sure what to do.
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData
(CheckforData()).
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]General network error. Check
your network documentation.
> Connection Broken
>
It could be several things... first a question: were any changes made or
different software installed on the computer running MSDE?
If not, databases like MSDE and SQL Server can expose network issues such as
packet drops or interruptions. Also, rule out name resolution problems like
DNS or WINS.
Another angle, consider installing the latest version of MDAC on the client
computer and enabling both SQL Server utilities TCP/IP and Named Pipes.
Steve
sql

Monday, March 26, 2012

Error during Merge Replication initialization

Hi,
We had a healthy 2-way merge replication set up with a SQL 2005
publisher/distributor and a SQL 2000 subscriber which had been running for
about a week. I re-created the publication so I could add automatic identity
range management to an article. I sucessfully re-created a push subscription
to a SQL 2005 subscriber but when I tried to create one to the same SQL 2000
machine that had been quite happy a few hours earlier, I kept getting this
error during initialization: "bulk data stream was incorrectly specified as
sorted". Nothing much has changed as far as I can see. Can anyone give me
some pointers?
Thanks,
Pete
Thanks for your response.
The collations were different and, having read about a similar problem on
another newsgroup, I changed the collation on my subscriber. The problem went
away so guess that fixed it. It's odd that the subscription had been
synchronizing fine up to the point that I changed the identity range
management options because I certainly didn't change the collation in between
dropping the subscriber and re-creating it. I'm sure there's a good reason
for it but it's no longer urgent.
Pete
"JPD" wrote:

> Hi Pete,
> Are you using the same collation on both the publishing database and the
> subscribing database? Have you tried using sp_dboption to set the
> select into/bulkcopy option of the subscriber database to ON?
> Jonathan
>
> Pete wrote:
>

Error During Job

We have getting an intermitant error when running
some of our Jobs.
ConnectionCheckForData (checkfordata)
[sqlstate 01000][message 10054]
General Network Error. Check Network Documentation
[sqlstat 08s01][error 11]
We can put retries on this step, and sometimes it
works after a couple of retries.. Other times
the job dies. If we restart the job, it will
usually complete.
We don't know why this is happening. The only thing
that step is doing is some inserts and deletes to a
couple of tables.
The connection problem seems to get worse as time goes
by... If we refresh the indexes, and do some other
database cleanup... it gets better.
Can anyone help us in preventing this problemanswered above - sometimes these newsgroups take a few minutes for posts to
appear...
Regards,
Greg Linwood
SQL Server MVP
"scot" <sstyer@.alltel.net> wrote in message
news:481001c42bcd$eff4bba0$a001280a@.phx.gbl...
> We have getting an intermitant error when running
> some of our Jobs.
> ConnectionCheckForData (checkfordata)
> [sqlstate 01000][message 10054]
> General Network Error. Check Network Documentation
> [sqlstat 08s01][error 11]
> We can put retries on this step, and sometimes it
> works after a couple of retries.. Other times
> the job dies. If we restart the job, it will
> usually complete.
> We don't know why this is happening. The only thing
> that step is doing is some inserts and deletes to a
> couple of tables.
> The connection problem seems to get worse as time goes
> by... If we refresh the indexes, and do some other
> database cleanup... it gets better.
> Can anyone help us in preventing this problem
>

error during installing SP3

Hi
I've got following error during installing SP3
by running this file Sql2kasp3.exe after successfully
installation sql 2ksp3.exe,
(SQL server 2000,server station)
"an error occurred during move data process : -145"
Thanks for any reply
--
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/Are you running analysis services?
--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"RM" <m_r1824@.yahoo.co.uk> wrote in message
news:opr1kakxwshqligo@.msnews.microsoft.com...
> Hi
> I've got following error during installing SP3
> by running this file Sql2kasp3.exe after successfully
> installation sql 2ksp3.exe,
> (SQL server 2000,server station)
> "an error occurred during move data process : -145"
> Thanks for any reply
> --
> Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/sql

error during installing SP3

quote:

> Hi
> I've got following error during installing SP3
> by running this file Sql2kasp3.exe after successfully
> installation sql 2ksp3.exe,
> (SQL server 2000,server station)
> "an error occurred during move data process : -145"
> Thanks for any reply
> --
> Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/

Wednesday, March 21, 2012

Error creating Subscription to reports

Hi all,

I am having a HUGE issue with SSRS, I am running SQL 2005 on Win 2003 server, the SQL uses SQL and windows permissions.

I have a datasource which stores it credentials securely on the server but for some reason when i try to subscribe to the report it errors saying

"Subscriptions cannot be created because the credentials used to run the report are not stored, or if a linked server the link is no longer valid."

Beats me but the credentials are stored, I am connecting using a user account which can run the report fine (This is proven).

I have SP1 installed, and have literally tried every last option in the book.

N.B i have read all the existing post about this and i seem to have a different issue, I am not using any paraeters in the report i am trying to test and i dont use anything like USR!USERID

Please help!

Andy

Anyone! I really need to get this running asap otherwise the upgrade and migration ot SSRS was pointless!!!|||

When you say “but the credentials are stored” what exactly you mean? Did you go to report properties and entered credentials and marked them to be stored in the database?

-Igor

|||when i say the credentials are stored i mean within the dataset, I have 1 shared dataset for a few reports and the dataset is set to store credentials securely on the server, I have set this in the designer (VS2005) and on the report server properties for the shared datasource but no joy.....|||

There might be one more less obvious reason - can you check server’s rsreportserver.config whether it has TimedSubscription and SnapshotUpdated event handlers configured? It should have something like this:

<Event>

<Type>ReportHistorySnapshotCreated</Type>

</Event>

</Extension>

<Event>

<Type>TimedSubscription</Type>

</Event>

</Extension>

<Event>

<Type>SnapshotUpdated</Type>

</Event>

</Extension>

</EventProcessing>

|||

I have this in my config file which looks good and as you mention, Im really struggling with this one and i hate being beaten so any help would be great.

<Event>

<Type>ReportHistorySnapshotCreated</Type>

</Event>

</Extension>

<Event>

<Type>TimedSubscription</Type>

</Event>

</Extension>

<Event>

<Type>SnapshotUpdated</Type>

</Event>

</Extension>

</EventProcessing>

|||

Lets take a look on the data source again. Please make sure: 1) Enable this data source check box is checked 2) Credentials stored securely in the report server radio button is selected 3) Use as Windows credentials when connecting to the data source check box is checked 5) Impersonate the authenticated user after a connection has been made to the data source check box in not checked 6) Windows integrated security radio button is not selected.

|||I have set all those options, (thats how i had them anyway) still no joy, I have tried this on another clean build server to make to make sure i am not going mad and still the same thing happens.|||

Andy,

Does your report have the User!UserID parameter? I have known a number of people complaint that when they use this parameter they are unable to create a subscription for their report and if they remove it then the subscription works. It's a shot in the dark but it's all I have so far.

Ham

|||

Andy,

Here's a link explaining why:

http://msdn2.microsoft.com/en-us/library/ms156012.aspx

Ham

|||

No joy that didnt change anything I dont use the user! param.

Still stuck. no joy here at all, any more ideas?

|||

Hello Andy

Have you got a solution? - please let us know if...

I experince the same issue AFTER stepping up from SQL 2005 Standard to Enterprise

Maybe it has something to do with some stale credentials residing from the restore

Does anybody know how to erase old passwords ?

Looking forward to hear from you

/ geert

denmark

Error creating Subscription to reports

Hi all,

I am having a HUGE issue with SSRS, I am running SQL 2005 on Win 2003 server, the SQL uses SQL and windows permissions.

I have a datasource which stores it credentials securely on the server but for some reason when i try to subscribe to the report it errors saying

"Subscriptions cannot be created because the credentials used to run the report are not stored, or if a linked server the link is no longer valid."

Beats me but the credentials are stored, I am connecting using a user account which can run the report fine (This is proven).

I have SP1 installed, and have literally tried every last option in the book.

N.B i have read all the existing post about this and i seem to have a different issue, I am not using any paraeters in the report i am trying to test and i dont use anything like USR!USERID

Please help!

Andy

Anyone! I really need to get this running asap otherwise the upgrade and migration ot SSRS was pointless!!!|||

When you say “but the credentials are stored” what exactly you mean? Did you go to report properties and entered credentials and marked them to be stored in the database?

-Igor

<Event>

<Type>ReportHistorySnapshotCreated</Type>

</Event>

</Extension>

<Event>

<Type>TimedSubscription</Type>

</Event>

</Extension>

<Event>

<Type>SnapshotUpdated</Type>

</Event>

</Extension>

</EventProcessing>

|||

I have this in my config file which looks good and as you mention, Im really struggling with this one and i hate being beaten so any help would be great.

<Event>

<Type>ReportHistorySnapshotCreated</Type>

</Event>

</Extension>

<Event>

<Type>TimedSubscription</Type>

</Event>

</Extension>

<Event>

<Type>SnapshotUpdated</Type>

</Event>

</Extension>

</EventProcessing>

|||

Andy,

Ham

|||

Andy,

Here's a link explaining why:

http://msdn2.microsoft.com/en-us/library/ms156012.aspx

Ham

|||

No joy that didnt change anything I dont use the user! param.

Still stuck. no joy here at all, any more ideas?

|||

Hello Andy

Have you got a solution? - please let us know if...

I experince the same issue AFTER stepping up from SQL 2005 Standard to Enterprise

Maybe it has something to do with some stale credentials residing from the restore

Does anybody know how to erase old passwords ?

Looking forward to hear from you

/ geert

denmark

sql

Monday, March 19, 2012

Error creating DB with numerical name?

Hi, all!! Using SQL 2000, latest patches and such; running under Win2k,
latest patches.
When I try to create a database with a numerical name (such as "12345"), I'm
getting an Incorrect Syntax error in code code (script) and in the Query
Analyzer. However, EntMgr will create it perfectly...
I just know this is going to be something simple, but derned if I can see
it... any ideas' :)
Thanks,
JackHi Jack
Put square brackets around any identifiers that don't follow the normal
rules for identifiers. (The normal rule for the identifies says they must
start with a letter, or one of a very few special chars, but not numbers.)
CREATE DATABASE [12345]
--
HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"Jack Black" <jackblackisback@.hotmail.com> wrote in message
news:OKH7EKusDHA.2932@.TK2MSFTNGP11.phx.gbl...
> Hi, all!! Using SQL 2000, latest patches and such; running under Win2k,
> latest patches.
> When I try to create a database with a numerical name (such as "12345"),
I'm
> getting an Incorrect Syntax error in code code (script) and in the Query
> Analyzer. However, EntMgr will create it perfectly...
> I just know this is going to be something simple, but derned if I can see
> it... any ideas' :)
> Thanks,
> Jack
>|||To add to Kalen's comments:
You might want to re-think this. Most developers stay away from names that doesn't confirms to the
rules for standard identifiers, as you have to always mess about with delimiters for the name when
you work against the data (and sooner or later you come across this great tools which doesn't
support delimited identifiers).
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Jack Black" <jackblackisback@.hotmail.com> wrote in message
news:OKH7EKusDHA.2932@.TK2MSFTNGP11.phx.gbl...
> Hi, all!! Using SQL 2000, latest patches and such; running under Win2k,
> latest patches.
> When I try to create a database with a numerical name (such as "12345"), I'm
> getting an Incorrect Syntax error in code code (script) and in the Query
> Analyzer. However, EntMgr will create it perfectly...
> I just know this is going to be something simple, but derned if I can see
> it... any ideas' :)
> Thanks,
> Jack
>

Friday, March 9, 2012

Error connecting to SQLExpress 2005 locally

Hello,
I'm a newbie here and was wondering anyone could help me with this.
I have a simple ASP.NET 2 web application running perfectly fine with
IIS and SQLServerExpress installed locally on my WinXP as a testing
server (I created the app in Visual Studio.NET 2005).
When deploying this app on the production server (running Win2000
Server, IIS and SQLServerExpress 2005), I'm getting the following
message when calling an aspx data-bound page from a browser:
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)
On the production server, I have the SQLServerExpress installed locally
on C: drive and the database is located on D: drive (on the same
directory as the app).
Connection string used in the webconfig file:
connectionString=" Server=SERVERNAME\SQLEXPRESS;AttachDbFil
ename=D:\Inetpub\A
pp_Data\registration. mdf;Database=registration;Trusted_Connec
tion=yes;"
providerName="System.Data.SqlClient"
Does anyone know how to solve this issue? Any help would be greatly
appreciated.
Thanks,
HarryHi
Have you checked if you are allowing remote connections on your SQL Express
installation, by default these will be switched off.
Check the Remote Connections setting the the SQL Server 2005 Surface Aread
Configuration tool.
John
"hko" wrote:

> Hello,
> I'm a newbie here and was wondering anyone could help me with this.
> I have a simple ASP.NET 2 web application running perfectly fine with
> IIS and SQLServerExpress installed locally on my WinXP as a testing
> server (I created the app in Visual Studio.NET 2005).
> When deploying this app on the production server (running Win2000
> Server, IIS and SQLServerExpress 2005), I'm getting the following
> message when calling an aspx data-bound page from a browser:
> 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)
> On the production server, I have the SQLServerExpress installed locally
> on C: drive and the database is located on D: drive (on the same
> directory as the app).
> Connection string used in the webconfig file:
> connectionString=" Server=SERVERNAME\SQLEXPRESS;AttachDbFil
ename=D:\Inetpub
\App_Data\registration. mdf;Database=registration;Trusted_Connec
tion=yes;"
> providerName="System.Data.SqlClient"
> Does anyone know how to solve this issue? Any help would be greatly
> appreciated.
> Thanks,
> Harry|||Hi John,
I did allow remote connections eventhough my database is on the same machine
as my web app, but no luck so far.
I used windows authentication for the database, and login to the machine
using admin account.
Another thing that I noticed is that when I go to SQL Server Configuration
Manager, under SQL Server 2005 Network Configuration, it says Protocols for
MSSQLSERVER, whereas on my dev machine it says SQLEXPRESS. When upgrading
from MSDE to SQLExpress i just chose the default instance name, but somehow
it's saying MSSQLSERVER.
I checked the databaseconnection through SQL Management Studio Express and
it works fine. Only when viewing the data-bound page on a browser that I get
the error message.
Do you think I should try to uninstall SQLServer Express and reinstall?
hko
"John Bell" wrote:
> Hi
> Have you checked if you are allowing remote connections on your SQL Expres
s
> installation, by default these will be switched off.
> Check the Remote Connections setting the the SQL Server 2005 Surface Aread
> Configuration tool.
> John
> "hko" wrote:
>|||Hi
If this is the default instance then change your connection string to only
be the servername.
If you want to change the installation from being the default instance you
will need to re-install.
John
"hko" wrote:
> Hi John,
> I did allow remote connections eventhough my database is on the same machi
ne
> as my web app, but no luck so far.
> I used windows authentication for the database, and login to the machine
> using admin account.
> Another thing that I noticed is that when I go to SQL Server Configuration
> Manager, under SQL Server 2005 Network Configuration, it says Protocols fo
r
> MSSQLSERVER, whereas on my dev machine it says SQLEXPRESS. When upgrading
> from MSDE to SQLExpress i just chose the default instance name, but someho
w
> it's saying MSSQLSERVER.
> I checked the databaseconnection through SQL Management Studio Express and
> it works fine. Only when viewing the data-bound page on a browser that I g
et
> the error message.
> Do you think I should try to uninstall SQLServer Express and reinstall?
> hko
> "John Bell" wrote:
>|||I only have one instance and that is the default instance, and this is my
connection string:
connectionString=" Server=HOMER\SQLEXPRESS;AttachDbFilename
=D:\Inetpub\App_Da
ta\registration. mdf;Database=registration;Trusted_Connec
tion=yes;"
providerName="System.Data.SqlClient"
Still something isn't right. Do you think I should probably re-install and
do fresh installation of SQL Express instead of upgrading (like what I did)?
"John Bell" wrote:
> Hi
> If this is the default instance then change your connection string to only
> be the servername.
> If you want to change the installation from being the default instance you
> will need to re-install.
> John
>
> "hko" wrote:
>|||Hi
Try the connection string:
connectionString=" Server=HOMER;AttachDbFilename=D:\Inetpub
\App_Data\registra
tion. mdf;Database=registration;Trusted_Connec
tion=yes;"
providerName="System.Data.SqlClient"
If you want a names instance then you would have to re-install and say that
you want a named instance and not the default instance.
John
"hko" wrote:
> I only have one instance and that is the default instance, and this is my
> connection string:
> connectionString=" Server=HOMER\SQLEXPRESS;AttachDbFilename
=D:\Inetpub\App_
Data\registration. mdf;Database=registration;Trusted_Connec
tion=yes;"
> providerName="System.Data.SqlClient"
> Still something isn't right. Do you think I should probably re-install and
> do fresh installation of SQL Express instead of upgrading (like what I did
)?
> "John Bell" wrote:
>|||Still not working. I tried different combination of connection strings but
kept getting the same error message.
I just want to use the default instance since there's only one database on
the machine.
I suspect there's a glitch during the upgrade process which causes SQL
server to locate the default instance. I was able to connect ok using
Management Studio Express.
This is the most frustrating thing ever to deal with...
"John Bell" wrote:
> Hi
> Try the connection string:
> connectionString=" Server=HOMER;AttachDbFilename=D:\Inetpub
\App_Data\regist
ration. mdf;Database=registration;Trusted_Connec
tion=yes;"
> providerName="System.Data.SqlClient"
> If you want a names instance then you would have to re-install and say tha
t
> you want a named instance and not the default instance.
> John
> "hko" wrote:
>|||Hi
A couple of suggestions:
Try using osql to try and connect, use both the server name and the IP
address and different user combinations.
Check that there is no blocking of the ports being used by a firewall (Try
telneting to the port!)
John
"hko" wrote:
> Still not working. I tried different combination of connection strings but
> kept getting the same error message.
> I just want to use the default instance since there's only one database on
> the machine.
> I suspect there's a glitch during the upgrade process which causes SQL
> server to locate the default instance. I was able to connect ok using
> Management Studio Express.
> This is the most frustrating thing ever to deal with...
> "John Bell" wrote:
>

Error Connecting To SQL 2005 through Webservice using SQL Authentication

Running a SQL 2005 Database under a Default instance. i.e. (SERVERNAME) and not (SERVERNAME/SQL2005)

I have a SQL Login sa password.

When I connect to SQL 2005 from anywhere other then the webservice it works fine.

In my webservice i am using System.Data.SqlClient.

SqlConnection, SqlCommand, SqlDataAdapter are being used to called a stored procedure and return the data into a System.Data.DataSet.

I get the following error when calling DataAdapter.Fill(dataSet);

{"TCP Provider: An existing connection was forcibly closed by the remote host.\r\n\r\nLogin failed for user 'sa'."}

I have no resolutions as of yet. Any help would be greatly appreciated.

Did you mean you can connect to the SQL2005 from anywhere with 'sa' login, except webservice? You can check the status of 'sa' login in management studio under Security->Logins, also make sure the Authentication Mode is SQL Server and Windows.|||

I have checked the status of the login for user "sa" and it has access rights and grant levels to everything it needs to.

I have also created a new account specifically for that database which does not work either. Same error.

And yes my SQL 2005 Instance is configured to use both SQL Authentication and Windows Authentication. (Mixed Mode).

Any Ideas?

|||

If you encountered this issue when you're trying to establish encrypted connection , you may take a look at this article:

http://blogs.msdn.com/sql_protocols/archive/2006/07/26/678596.aspx

Wednesday, March 7, 2012

Error connecting to SQL 2000 remotely

We are trying to connect to a specific database on an instance of SQL 2000
(there are two instances on this server) running on W2K.
However when we try and login (the username and password are correct) we
receive the following error:
Server Error in '/SimplyWeb' Application.
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)
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information about
the error and where it originated in the code.
Exception Details: System.Data.SqlClient.SqlException: 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)
Source Error:
An unhandled exception was generated during the execution of the current web
request. Information regarding the origin and location of the exception can
be identified using the exception stack trace below.
Stack Trace:
[SqlException (0x80131904): 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)]
BusinessRules.IUsers.clsIUsers..ctor(String InUserName) +54
SimplyWebPersonnel.Login.Login.LoginClick(Object sender, ButtonEventArgs
e) +517
Infragistics.WebUI.WebDataInput.WebImageButton.OnC lick(Int32 action) +91
Infragistics.WebUI.WebControls.Buttons.WebButtonBa se.System.Web.UI.IPostBackDataHandler.RaisePostDat aChangedEvent() +18
System.Web.UI.Page.RaiseChangedEvents() +137
System.Web.UI.Page.ProcessRequestMain(Boolean
includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +4778
Version Information: Microsoft .NET Framework Version:2.0.50727.832; ASP.NET
Version:2.0.50727.832
Any ideas or hints to allow remote connections to a SQL 2000 server?
The hint would be simple: a bit more study on SQL Server configuration. Look
into these:
1. Does the SQL Server instance allow remote connection (from other
computer?)
2. Does the SQL Server use SQL Server security - mixed security mode -
(using username/password in connectionString)?
If you can clearly answer these two questions, and still have problem, then
you have to show some code, especially the ConnectionString, and describe
more details.
"Simon" <Simon@.discussions.microsoft.com> wrote in message
news:EFC3F694-126C-473B-AD0B-AA59ACCF0411@.microsoft.com...
> We are trying to connect to a specific database on an instance of SQL 2000
> (there are two instances on this server) running on W2K.
> However when we try and login (the username and password are correct) we
> receive the following error:
> Server Error in '/SimplyWeb' Application.
> ----
> 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)
> Description: An unhandled exception occurred during the execution of the
> current web request. Please review the stack trace for more information
> about
> the error and where it originated in the code.
> Exception Details: System.Data.SqlClient.SqlException: 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)
> Source Error:
> An unhandled exception was generated during the execution of the current
> web
> request. Information regarding the origin and location of the exception
> can
> be identified using the exception stack trace below.
> Stack Trace:
>
> [SqlException (0x80131904): 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)]
> BusinessRules.IUsers.clsIUsers..ctor(String InUserName) +54
> SimplyWebPersonnel.Login.Login.LoginClick(Object sender, ButtonEventArgs
> e) +517
> Infragistics.WebUI.WebDataInput.WebImageButton.OnC lick(Int32 action) +91
> Infragistics.WebUI.WebControls.Buttons.WebButtonBa se.System.Web.UI.IPostBackDataHandler.RaisePostDat aChangedEvent()
> +18
> System.Web.UI.Page.RaiseChangedEvents() +137
> System.Web.UI.Page.ProcessRequestMain(Boolean
> includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +4778
>
>
> ----
> Version Information: Microsoft .NET Framework Version:2.0.50727.832;
> ASP.NET
> Version:2.0.50727.832
>
> Any ideas or hints to allow remote connections to a SQL 2000 server?
|||Found out I had brackets around the server name. Now getting a different
error, this time:
(provider: Named Pipes Provider, error: 40 - Could not open a connection to
SQL Server)
SqlException (0x80131904): An error has occurred while establishing a
connection to the server.
I have checked that named pipes and TCP/IP are allowed. What should the
named pipes string look like for connecting to a local database?
"Norman Yuan" wrote:

> The hint would be simple: a bit more study on SQL Server configuration. Look
> into these:
> 1. Does the SQL Server instance allow remote connection (from other
> computer?)
> 2. Does the SQL Server use SQL Server security - mixed security mode -
> (using username/password in connectionString)?
> If you can clearly answer these two questions, and still have problem, then
> you have to show some code, especially the ConnectionString, and describe
> more details.
>
> "Simon" <Simon@.discussions.microsoft.com> wrote in message
> news:EFC3F694-126C-473B-AD0B-AA59ACCF0411@.microsoft.com...
>

Error connecting to SQL 2000 remotely

We are trying to connect to a specific database on an instance of SQL 2000
(there are two instances on this server) running on W2K.
However when we try and login (the username and password are correct) we
receive the following error:
Server Error in '/SimplyWeb' Application.
----
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)
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information about
the error and where it originated in the code.
Exception Details: System.Data.SqlClient.SqlException: 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)
Source Error:
An unhandled exception was generated during the execution of the current web
request. Information regarding the origin and location of the exception can
be identified using the exception stack trace below.
Stack Trace:
[SqlException (0x80131904): 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)]
BusinessRules.IUsers.clsIUsers..ctor(String InUserName) +54
SimplyWebPersonnel.Login.Login.LoginClick(Object sender, ButtonEventArgs
e) +517
Infragistics.WebUI.WebDataInput.WebImageButton.OnClick(Int32 action) +91
Infragistics.WebUI.WebControls.Buttons.WebButtonBase.System.Web.UI.IPostBackDataHandler.RaisePostDataChangedEvent() +18
System.Web.UI.Page.RaiseChangedEvents() +137
System.Web.UI.Page.ProcessRequestMain(Boolean
includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +4778
----
Version Information: Microsoft .NET Framework Version:2.0.50727.832; ASP.NET
Version:2.0.50727.832
Any ideas or hints to allow remote connections to a SQL 2000 server?The hint would be simple: a bit more study on SQL Server configuration. Look
into these:
1. Does the SQL Server instance allow remote connection (from other
computer?)
2. Does the SQL Server use SQL Server security - mixed security mode -
(using username/password in connectionString)?
If you can clearly answer these two questions, and still have problem, then
you have to show some code, especially the ConnectionString, and describe
more details.
"Simon" <Simon@.discussions.microsoft.com> wrote in message
news:EFC3F694-126C-473B-AD0B-AA59ACCF0411@.microsoft.com...
> We are trying to connect to a specific database on an instance of SQL 2000
> (there are two instances on this server) running on W2K.
> However when we try and login (the username and password are correct) we
> receive the following error:
> Server Error in '/SimplyWeb' Application.
> ----
> 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)
> Description: An unhandled exception occurred during the execution of the
> current web request. Please review the stack trace for more information
> about
> the error and where it originated in the code.
> Exception Details: System.Data.SqlClient.SqlException: 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)
> Source Error:
> An unhandled exception was generated during the execution of the current
> web
> request. Information regarding the origin and location of the exception
> can
> be identified using the exception stack trace below.
> Stack Trace:
>
> [SqlException (0x80131904): 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)]
> BusinessRules.IUsers.clsIUsers..ctor(String InUserName) +54
> SimplyWebPersonnel.Login.Login.LoginClick(Object sender, ButtonEventArgs
> e) +517
> Infragistics.WebUI.WebDataInput.WebImageButton.OnClick(Int32 action) +91
> Infragistics.WebUI.WebControls.Buttons.WebButtonBase.System.Web.UI.IPostBackDataHandler.RaisePostDataChangedEvent()
> +18
> System.Web.UI.Page.RaiseChangedEvents() +137
> System.Web.UI.Page.ProcessRequestMain(Boolean
> includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +4778
>
>
> ----
> Version Information: Microsoft .NET Framework Version:2.0.50727.832;
> ASP.NET
> Version:2.0.50727.832
>
> Any ideas or hints to allow remote connections to a SQL 2000 server?|||Found out I had brackets around the server name. Now getting a different
error, this time:
(provider: Named Pipes Provider, error: 40 - Could not open a connection to
SQL Server)
SqlException (0x80131904): An error has occurred while establishing a
connection to the server.
I have checked that named pipes and TCP/IP are allowed. What should the
named pipes string look like for connecting to a local database?
"Norman Yuan" wrote:
> The hint would be simple: a bit more study on SQL Server configuration. Look
> into these:
> 1. Does the SQL Server instance allow remote connection (from other
> computer?)
> 2. Does the SQL Server use SQL Server security - mixed security mode -
> (using username/password in connectionString)?
> If you can clearly answer these two questions, and still have problem, then
> you have to show some code, especially the ConnectionString, and describe
> more details.
>
> "Simon" <Simon@.discussions.microsoft.com> wrote in message
> news:EFC3F694-126C-473B-AD0B-AA59ACCF0411@.microsoft.com...
> > We are trying to connect to a specific database on an instance of SQL 2000
> > (there are two instances on this server) running on W2K.
> >
> > However when we try and login (the username and password are correct) we
> > receive the following error:
> >
> > Server Error in '/SimplyWeb' Application.
> > ----
> >
> > 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)
> > Description: An unhandled exception occurred during the execution of the
> > current web request. Please review the stack trace for more information
> > about
> > the error and where it originated in the code.
> >
> > Exception Details: System.Data.SqlClient.SqlException: 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)
> >
> > Source Error:
> >
> > An unhandled exception was generated during the execution of the current
> > web
> > request. Information regarding the origin and location of the exception
> > can
> > be identified using the exception stack trace below.
> >
> > Stack Trace:
> >
> >
> > [SqlException (0x80131904): 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)]
> > BusinessRules.IUsers.clsIUsers..ctor(String InUserName) +54
> > SimplyWebPersonnel.Login.Login.LoginClick(Object sender, ButtonEventArgs
> > e) +517
> > Infragistics.WebUI.WebDataInput.WebImageButton.OnClick(Int32 action) +91
> >
> > Infragistics.WebUI.WebControls.Buttons.WebButtonBase.System.Web.UI.IPostBackDataHandler.RaisePostDataChangedEvent()
> > +18
> > System.Web.UI.Page.RaiseChangedEvents() +137
> > System.Web.UI.Page.ProcessRequestMain(Boolean
> > includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +4778
> >
> >
> >
> >
> > ----
> > Version Information: Microsoft .NET Framework Version:2.0.50727.832;
> > ASP.NET
> > Version:2.0.50727.832
> >
> >
> > Any ideas or hints to allow remote connections to a SQL 2000 server?
>

Error connecting to SQL 2000 remotely

We are trying to connect to a specific database on an instance of SQL 2000
(there are two instances on this server) running on W2K.
However when we try and login (the username and password are correct) we
receive the following error:
Server Error in '/SimplyWeb' Application.
----
--
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/Instanc
e
Specified)
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information abou
t
the error and where it originated in the code.
Exception Details: System.Data.SqlClient.SqlException: An error has occurred
while establishing a connection to the server. When connecting to SQL Serve
r
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)
Source Error:
An unhandled exception was generated during the execution of the current web
request. Information regarding the origin and location of the exception can
be identified using the exception stack trace below.
Stack Trace:
[SqlException (0x80131904): 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 no
t
allow remote connections. (provider: SQL Network Interfaces, error: 26 -
Error Locating Server/Instance Specified)]
BusinessRules.IUsers.clsIUsers..ctor(String InUserName) +54
SimplyWebPersonnel.Login.Login.LoginClick(Object sender, ButtonEventArgs
e) +517
Infragistics.WebUI.WebDataInput.WebImageButton.OnClick(Int32 action) +91
Infragistics.WebUI.WebControls.Buttons.WebButtonBase.System.Web.UI.IPostBack
DataHandler.RaisePostDataChangedEvent() +18
System.Web.UI.Page.RaiseChangedEvents() +137
System.Web.UI.Page.ProcessRequestMain(Boolean
includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +4778
----
--
Version Information: Microsoft .NET Framework Version:2.0.50727.832; ASP.NET
Version:2.0.50727.832
Any ideas or hints to allow remote connections to a SQL 2000 server?The hint would be simple: a bit more study on SQL Server configuration. Look
into these:
1. Does the SQL Server instance allow remote connection (from other
computer?)
2. Does the SQL Server use SQL Server security - mixed security mode -
(using username/password in connectionString)?
If you can clearly answer these two questions, and still have problem, then
you have to show some code, especially the ConnectionString, and describe
more details.
"Simon" <Simon@.discussions.microsoft.com> wrote in message
news:EFC3F694-126C-473B-AD0B-AA59ACCF0411@.microsoft.com...
> We are trying to connect to a specific database on an instance of SQL 2000
> (there are two instances on this server) running on W2K.
> However when we try and login (the username and password are correct) we
> receive the following error:
> Server Error in '/SimplyWeb' Application.
> ----
--
> 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)
> Description: An unhandled exception occurred during the execution of the
> current web request. Please review the stack trace for more information
> about
> the error and where it originated in the code.
> Exception Details: System.Data.SqlClient.SqlException: 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)
> Source Error:
> An unhandled exception was generated during the execution of the current
> web
> request. Information regarding the origin and location of the exception
> can
> be identified using the exception stack trace below.
> Stack Trace:
>
> [SqlException (0x80131904): 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)]
> BusinessRules.IUsers.clsIUsers..ctor(String InUserName) +54
> SimplyWebPersonnel.Login.Login.LoginClick(Object sender, ButtonEventArgs
> e) +517
> Infragistics.WebUI.WebDataInput.WebImageButton.OnClick(Int32 action) +91
> Infragistics.WebUI.WebControls.Buttons.WebButtonBase.System.Web.UI.IPostBa
ckDataHandler.RaisePostDataChangedEvent()
> +18
> System.Web.UI.Page.RaiseChangedEvents() +137
> System.Web.UI.Page.ProcessRequestMain(Boolean
> includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +4778
>
>
> ----
--
> Version Information: Microsoft .NET Framework Version:2.0.50727.832;
> ASP.NET
> Version:2.0.50727.832
>
> Any ideas or hints to allow remote connections to a SQL 2000 server?|||Found out I had brackets around the server name. Now getting a different
error, this time:
(provider: Named Pipes Provider, error: 40 - Could not open a connection to
SQL Server)
SqlException (0x80131904): An error has occurred while establishing a
connection to the server.
I have checked that named pipes and TCP/IP are allowed. What should the
named pipes string look like for connecting to a local database?
"Norman Yuan" wrote:

> The hint would be simple: a bit more study on SQL Server configuration. Lo
ok
> into these:
> 1. Does the SQL Server instance allow remote connection (from other
> computer?)
> 2. Does the SQL Server use SQL Server security - mixed security mode -
> (using username/password in connectionString)?
> If you can clearly answer these two questions, and still have problem, the
n
> you have to show some code, especially the ConnectionString, and describe
> more details.
>
> "Simon" <Simon@.discussions.microsoft.com> wrote in message
> news:EFC3F694-126C-473B-AD0B-AA59ACCF0411@.microsoft.com...
>

Error Connecting to DB

I downloaded an ASP.NET web application from the web to learn the .NET framework. I was successful in running the website on my laptop using ASP.NET Development Server that comes with Visual Studio 2005. My laptop is running Windows XP Professional and SQL Server 2005. I am now trying to do the same on my desktop computer running Windows Vista; however, for some reason i am getting an error when the website tries to connect to the DB. Here are the steps i have followed so far:

1. I tried to configure the website DB connection the same way i configured it on my laptop. Basically I use the following connectionStrings:

<connectionStrings>
<remove name="LocalSqlServer"/>
<add name="LocalSqlServer" connectionString="Data Source=localhost;Initial Catalog=TheBeerHouse;Integrated Security=True" providerName="System.Data.SqlClient"/>
</connectionStrings
2. That same connection string worked fine on my laptop. But I got the following error on my desktop:

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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

I am wondering if the error is related to Vista. When i try to connect to that DB using SQL Management Studio via Windows Authetication and do not run it as Administrator then I cannot connect to the DB. In other words, only when i run SQL Management Studio as administrator i am able to use Windows authentication to connect to that DB.

3. Next, I tried creating a SQL login. I made sure I can use that login to access the DB directly using SQL Management Studio. In addition, I changed the database to allow "Local and remote connections" "Using both TCP/IP and named pipes".

4. Changed the connectionStrings in web.config to:

<connectionStrings>
<remove name="LocalSqlServer"/>
<add name="LocalSqlServer" connectionString="Data Source=localhost;Initial Catalog=TheBeerHouse;Integrated Security=False;uid=*****pwd=****" providerName="System.Data.SqlClient"/>
</connectionStrings
Obviously, the actual connectionString has the actual user name i created and the correct password instead of (*) asterisks.

5. And once again, I got same error as above

Any help will be appreciated!

Hi,

Is sqlserver on your desktop running in "Windows Authentication Mode" or "Mixed Mode"

Open up SqlServer Management Studio, right click on the Server, not the database(s), then in the left hand menu shown select Security. The dialog box on the right should have"SQL Server and Window Authentication Mode" checked instead of just"Windows Authentication Mode".

Hope this helps

Regards

ScottyB

|||

I have "SQL Server and Window Authentication Mode"checked. I can login directly to the database via SQL Managament Studio using the same login and password as specified in the connectionString. I also have allowedLocal and remote connections and haveUsingboth TCP/IP and named pipeschecked.

|||

Hi nj07208

I have just noticed in the connection string that you posted here that you do not have a semiclon after the uid and pwd parameters. You can try this. See the listings below

Original Connection String

<connectionStrings> <remove name="LocalSqlServer"/> <add name="LocalSqlServer" connectionString="Data Source=localhost;Initial Catalog=TheBeerHouse;Integrated Security=False;uid=*****pwd=****" providerName="System.Data.SqlClient"/> </connectionStrings>

Modified Connection String

<connectionStrings> <remove name="LocalSqlServer"/> <add name="LocalSqlServer" connectionString="Data Source=localhost;Initial Catalog=TheBeerHouse;Integrated Security=False;uid=*****;pwd=****"; providerName="System.Data.SqlClient"/> </connectionStrings>

Regards

ScottyB

|||

i guess you meant with the semicolon right after the password before the double quotes. I tried that and it didn't work =(

|||

I got a new error now! I turned off my firewalls (both Windows and McAfee ViruScan) and now i get a new error:

Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached.

Any ideas?

|||

If you have access to the iismanager try doing a pool reset or a iisreset.

Do you have any code in your application that goes through a loop and opens connections. This error may suggest you are opening connections faster than the garbage collector can dispose of them.

Regards

ScottyB

|||

I am using ASP.NET Development Server that comes with Visual Studio 2005. I am not using IIS.

|||

I got it!!! It works now!!! On the connectionString i changed Data Source from localhost to localhost\SQLEXPRESS. This is needed because I am using a named instance. So, to recap for anyone who is interested, these are the steps i followed:

1. EnableSQL Server and Windows Authentication mode. This can be done from SQL Management Studio

2. Create SQL Server login. Make sure you can login to the database using SQL Management Studio

3. EnableLocal and remote connections and haveUsingboth TCP/IP and named pipeschecked. This can be done from SQL Server Surface Area Configuration.

4. Connection String on web.config should be the following

<connectionStrings> <remove name="LocalSqlServer"/> <add name="LocalSqlServer" connectionString="Data Source=localhost\SQLEXPRESS;Initial Catalog=TheBeerHouse;Integrated Security=False;uid=username;pwd=password;" providerName="System.Data.SqlClient"/></connectionStrings>

Note that I enabled both Windows and McAvfee AntiVirus firewalls and it still works.

Sunday, February 26, 2012

Error connecting in Management Studio

Hello,

I am having problems connecting to my SQL Server instance with Management Studio; basically the setup is as follows;

*Single server running windows 2003 enterprise - in a workgroup not domain
*SQL Server is installed on this machine
*When I try and connect from the same machine using its own IP address and Windows authentication I get the 18452 error "login failed for {NULL} user"

I am testing it like this because Sharepoint is failing in configuration wizard because it is connecting the same way - at least the login failure audit logs say the same.

Many thanks for answers

With which application are you trying to connect ? Did you try another application yet ?

Jens K. Suessmeyer

http://www.sqlserver2005.de

|||

This commonly happens with trusted authentication when your local user does not translate to the other machine (e.g. LOCAL_SYSTEM or NETWORK_SERVICE, etc.). Naturally, if you translate to the IP address, even on loopback, the account must be one that can be understood remotely, so in this case your client and server are the same machine, but the same truth applies. Your user must be recognizable from a remote connection to this machine. Try rasing into the machine from a remote machine under the user account to see if it works. If it doesn't ras, your user needs to be reconfigured/reselected.

http://www.microsoft.com/technet/prodtechnol/windows2000serv/deploy/confeat/ias2000a.mspx

http://ablog.apress.com/?p=1127

http://support.microsoft.com/kb/215383

http://www.microsoft.com/technet/prodtechnol/windows2000serv/deploy/confeat/kerberos.mspx

It could also be possible that your machine is not running the correct authentication protocols to support Trusted authentication on your OS. I don't actually know how to configure users/authentication on Windows workgroups/domains so how this is addressed is beyond me.

Hope that helps,

John

|||Thanks for the response John.

The user I am using is the default "Administrator" (I know bad practice) for testing.

It is definatly something to do with the user not being understood in the loopback.

However like you, I have no idea how to fix this :/

Cheers
|||Try a different user or modifying your administrative user to have remote access. Administrator is one of those users that is traditionally a local account only. Optionally, you could try fiddling with the user manager and enabling remote access for the administrator account, but I am fairly certain that would open you up to some evil attacks.|||Can you tell us how you connect exactly?
Are you using OPENROWSET?

Thursday, March 29, 2012

Error executing SSIS package

Error executing SSIS package

Error executing SSIS package

error executing query

error executing query

error executing query

Monday, March 26, 2012

Error during Merge Replication initialization

Error During Job

error during installing SP3

error during installing SP3

Wednesday, March 21, 2012

Error creating Subscription to reports

Error creating Subscription to reports

Monday, March 19, 2012

Error creating DB with numerical name?

Friday, March 9, 2012

Error connecting to SQLExpress 2005 locally

Error Connecting To SQL 2005 through Webservice using SQL Authentication

Wednesday, March 7, 2012

Error connecting to SQL 2000 remotely

Error connecting to SQL 2000 remotely

Error connecting to SQL 2000 remotely

Error Connecting to DB

Sunday, February 26, 2012

Error connecting in Management Studio

Error accessing report

Blog Archive

About Me