Error when trying to change server settings

I am trying to connect to a SQL Server machine using SQL security instead of integrgated security. However, the server was setup initially to use only integrated security. When I right click on the server and select properties, I get this error:

Error 0: Cannot load the DLL xpstar.dll, or one of the DLLs it references. Reason: 5(Access is denied.).

I googled this error but could not find a single solution. The dll will not register with regsvr32. Do I need to repair SQL Server and then re-run the latest service pack, or is there a simple solution?

Thanks,Books Online

How to set up Mixed Mode security (Enterprise Manager)
To set up Mixed Mode security

Expand a server group.

Right-click a server, and then click Properties.

Click the Security tab.

Under Authentication, click SQL Server and Windows.

Under Audit level, select the level at which user accesses to Microsoft® SQL Server? are recorded in the SQL Server error log:
None causes no auditing to be performed.

Success causes only successful login attempts to be audited.

Failure causes only failed login attempts to be audited.

All causes successful and failed login attempts to be audited.

See Also

Authentication Modes
------

Does that help?|||Thanks. I understand how to setup mixed mode security, but the problem appears to be a dll called xpstar.dll which throws an error when I right click on the server icon and select properties. I wanted to know if there was a fix for this short of reinstalling.

When I right click on the server icon in server explorer and select properties, I get this error:

Error 0: Cannot load the DLL xpstar.dll, or one of the DLLs it references. Reason: 5(Access is denied.).

I googled this error but could not find a single solution. The dll will not register with regsvr32. Do I need to repair SQL Server and then re-run the latest service pack, or is there a simple solution?|||No answers, just questions.

What version & service pack of SQL Server are you running?

Have you checked the event log to see if you can find any further information?

Terri|||Hello Terri,

It is SQL Server 2000 and should have service pack 3 installed.

There are no errors in the event log related to SQL Server.|||Is there anything in the SQL Server Logs?

Terri|||Unfortunately not.

Also, I reapplied Service Pack 3 and it did not fix the problem.

I have SQL on a development machine. If I right click on the local server instance and then select properties, the Server properties dialog appears. If I select the server, I get an error. At first, I thought it was the development machine, but unfortunately the same thing happens when I try this directly on the server. I am at a loss of what to do short of backing up the databases, uninstalling SQL, reinstalling SQL, and then restoring the databases. The SQL installation does not have a repair option - do you know what would happen if I installed SQL over the existing SQL?

Thanks,

Error when running Tuning advisor

When I try to launch the tuning advisor, I get this error - Any help will be much appriciated.

===================================

Failed to connect to an IPC Port: The system cannot find the file specified.
(mscorlib)

Program Location:

Server stack trace:
at System.Runtime.Remoting.Channels.Ipc.IpcPort.Connect(String portName, Boolean secure, TokenImpersonationLevel impersonationLevel, Int32 timeout)
at System.Runtime.Remoting.Channels.Ipc.ConnectionCache.GetConnection(String portName, Boolean secure, TokenImpersonationLevel level, Int32 timeout)
at System.Runtime.Remoting.Channels.Ipc.IpcClientTransportSink.ProcessMessage(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream, ITransportHeaders& responseHeaders, Stream& responseStream)
at System.Runtime.Remoting.Channels.BinaryClientFormatterSink.SyncProcessMessage(IMessage msg)

Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at Microsoft.SqlServer.Management.UI.VSIntegration.ISessionController.CreateSessionFromQuery(SqlConnectionInfo connectionInfo, String sqlQuery, String batchSeparator)
at Microsoft.SqlServer.Management.UI.VSIntegration.Editors.SqlScriptEditorControl.OnDatabaseTuningAdvisor(Object sender, EventArgs a)

What is the service pack level on SQL Server?

Any recent changes to the server and client machine you are using, such as automatic updates?

|||Hi,

I had got the same error when I tried to tune my query.

However after I click "OK" button of the Error message, in few seconds the "Tuning Adviser" window opens but it is not connected to the session of the query editor (in which the query was executed).

Now without closing this tuning adviser window, if I again click on Analyser button, the analyser opens fine and the query is also tunned properly.

Let me know if this works for you too.

Regards,

Shweta

Error when Logging on - Error: 18456, Severity: 14, State: 16

Hi All,
I am getting the following error in the ERRORLOG File when I am
trying
to connect to SQL Server 2005 Express Edition from the command line.
2007-03-23 07:30:05.54 Logon Error: 18456, Severity: 14, State:
16.
2007-03-23 07:30:05.54 Logon Login failed for user 'sa'.
[CLIENT: xx.xx.xx.xx]
I have a fresh install of SQL Server on my local machine, which is
probably the source of my angst, but I am trying to create a database
from scratch through using a batch file that is run from the command
line, the batch file looks like this:
<snip>
SQLCMD -U %USR% -P %PWD% -S %SVR% -d %DBF% -i CreateDatabase.sql
<snip>
The values of %USR% and %PWD% are correct as I frequently log into
Management Studio with the details, %SVR% is "<ComputerName>
\SQLEXPRESS,1433" and %DBF% is <DatabaseName>. The contents of
CreateDatabase.sql when run in Management Studio successfully creates
the database that I require so I know the error doesn't lie there.
The command line error that is showing reads as the following:
Msg 4060, Level 11, State 1, Server <ComputerName>\SQLEXPRESS, Line 1
Cannot open database "<DatabaseName>" requested by the login. The
login failed.
Msg 18456, Level 14, State 1, Server <ComputerName>\SQLEXPRESS, Line
1
Login failed for user 'sa'.
I have a feeling that it is related to 'sa' not having the correct
permissions with regards to logging into or creating a database from
scratch, but I find it odd that I can login as 'sa' in Management
Studio and create the database from there, but when I try it from the
command-line (despite having TCP/IP enabled) it won't let me connect
to create a database.
Is there something I am missing here? I have been banging my head off
of walls for days over this and am unsure of the next steps to take.
If any of this screams "why the hell are you doing this?" then please
let me know as at the moment I am punching in the dark with this
problem, I have searched Usenet, Google Groups, the Web and although
I
have found potential solutions to this particular problem I am
having,
nothing I have done so far has actually managed to fix the issue.
Related articles I have followed are:
Login failed for user 'x'
http://msdn2.microsoft.com/en-us/library/ms366351.aspx
Change Server Authentication Mode
http://msdn2.microsoft.com/en-us/library/ms188670.aspx
Upgrading MSDE 2000 to SQL Server 2005 Express [Enabling network
protocols section]
http://www.microsoft.com/technet/pr...e2sqlexpress...
NOTE: I just listed these articles to show what path I am currently
looking at with regards to this problem, but again I stress I have
found nothing yet to get round this problem, and any further articles
or direction would be much appreciated.
Yours Distressingly
AlastairI'm still not clear on what database is used for -d
<DatabaseName> and this could be one of the problems. If you
are trying to log in using the database you are about to
create, then that's likely the issue as it doesn't exist
when logging in. Try specifying master for the initial login
database.
-Sue
On 23 Mar 2007 08:48:10 -0700, "Alastair"
<alastair_anderson@.hotmail.com> wrote:

>Hi All,
>I am getting the following error in the ERRORLOG File when I am
>trying
>to connect to SQL Server 2005 Express Edition from the command line.
>
>2007-03-23 07:30:05.54 Logon Error: 18456, Severity: 14, State:
>16.
>2007-03-23 07:30:05.54 Logon Login failed for user 'sa'.
>[CLIENT: xx.xx.xx.xx]
>
>I have a fresh install of SQL Server on my local machine, which is
>probably the source of my angst, but I am trying to create a database
>from scratch through using a batch file that is run from the command
>line, the batch file looks like this:
>
><snip>
>SQLCMD -U %USR% -P %PWD% -S %SVR% -d %DBF% -i CreateDatabase.sql
><snip>
>
>The values of %USR% and %PWD% are correct as I frequently log into
>Management Studio with the details, %SVR% is "<ComputerName>
>\SQLEXPRESS,1433" and %DBF% is <DatabaseName>. The contents of
>CreateDatabase.sql when run in Management Studio successfully creates
>the database that I require so I know the error doesn't lie there.
>
>The command line error that is showing reads as the following:
>
>Msg 4060, Level 11, State 1, Server <ComputerName>\SQLEXPRESS, Line 1
>Cannot open database "<DatabaseName>" requested by the login. The
>login failed.
>Msg 18456, Level 14, State 1, Server <ComputerName>\SQLEXPRESS, Line
>1
>Login failed for user 'sa'.
>
>I have a feeling that it is related to 'sa' not having the correct
>permissions with regards to logging into or creating a database from
>scratch, but I find it odd that I can login as 'sa' in Management
>Studio and create the database from there, but when I try it from the
>command-line (despite having TCP/IP enabled) it won't let me connect
>to create a database.
>
>Is there something I am missing here? I have been banging my head off
>of walls for days over this and am unsure of the next steps to take.
>
>If any of this screams "why the hell are you doing this?" then please
>let me know as at the moment I am punching in the dark with this
>problem, I have searched Usenet, Google Groups, the Web and although
>I
>have found potential solutions to this particular problem I am
>having,
>nothing I have done so far has actually managed to fix the issue.
>
>Related articles I have followed are:
>
>Login failed for user 'x'
>http://msdn2.microsoft.com/en-us/library/ms366351.aspx
>
>Change Server Authentication Mode
>http://msdn2.microsoft.com/en-us/library/ms188670.aspx
>
>Upgrading MSDE 2000 to SQL Server 2005 Express [Enabling network
>protocols section]
>http://www.microsoft.com/technet/pr...e2sqlexpress...
>
>NOTE: I just listed these articles to show what path I am currently
>looking at with regards to this problem, but again I stress I have
>found nothing yet to get round this problem, and any further articles
>or direction would be much appreciated.
>
>Yours Distressingly
>
>Alastair|||On 25 Mar, 16:17, Sue Hoegemeier <S...@.nomail.please> wrote:
> I'm still not clear on what database is used for -d
> <DatabaseName> and this could be one of the problems. If you
> are trying to log in using the database you are about to
> create, then that's likely the issue as it doesn't exist
> when logging in. Try specifying master for the initial login
> database.
> -Sue
> On 23 Mar 2007 08:48:10 -0700, "Alastair"
>
> <alastair_ander...@.hotmail.com> wrote:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> - Show quoted text -
You managed to hit the nail on the head.
Running my current script when the new database already exists it
works fine, however for a fresh install of SQL Server, when it doesn't
currently exist then it doesn't work.
Thanks for your help
Alastair

Error when i try to Deploy my reports to Reporting services - PLEASE HELP i'm also NEW at t

Hi

I'm running a SQL 2000 DB with reporting Services 2005 and Visual Studio 2005, I can connect and browse to Reporting Services through any management console and even to my site through //ServerName/Reports but when i try to deploy any of my reports to the Reporting Services through my VS2005 solution i get this error

A connection could not be made to the report server http://Forge/Reports.

Additional Information:

The Attempt to connect to the report server failed. Check your connection information and that the report server is a compatible version. (Microsoft.ReportingServices.Designer)

The status of all of my things in Reporting Services Configuration is Green and i can see my site in the IIS, i can also browse my site, it just doesn't want2 deploy.

Please HELP!!!

I suspect the problem lies here:

>I'm running a SQL 2000 DB with reporting Services 2005 and Visual Studio 2005

and, considering the error:

>that the report server is a compatible version

I am thinking there is a problem with your deploying RS 2005 reports to a 2000 RS database. I wasn't aware you could deploy 2005 reports to a 2000 RS database. Maybe you can do it if you don't convert (existing 2000) reports, I am not sure; but I doubt you'll be able to deploy them if you have converted them from 2000 to 2005. I especially think and new reports will bomb out since they would be native 2005.

There are threads in this forum that talk about this subject.

|||Try deploying to http://forge/reportserver instead.|||wow. good eye!|||

Thanks for th information but it still gives me the same error, but don't worry too much about it, i'm just going to reinstall SQL 2000 RS with Visual Studio 2003. apparently there is some incompatibility issue between .Net Framework 2.0 and 1.1 that prevent my solutions from working properly, so until i figure out the exact problem and link the Frameworks manually in my solution i doubt that it will work.

Thanks a lot for your effort guys!

|||

Hi

I traced down my problem, but i'll post my solution here just incase some else might battle with the same problem.

When i installed the RS i changed the Virtual Directory Name to Forge too, so when i deployed them i had to deploy them to Forge/Forge instead of Forge/ReportServer which it suppose to be by default. ->PC Name / ReportServer Virtual Directory<--

Error when i try to Deploy my reports to Reporting services - PLEASE HELP i'm also NEW at t

Hi

I'm running a SQL 2000 DB with reporting Services 2005 and Visual Studio 2005, I can connect and browse to Reporting Services through any management console and even to my site through //ServerName/Reports but when i try to deploy any of my reports to the Reporting Services through my VS2005 solution i get this error

A connection could not be made to the report server http://Forge/Reports.

Additional Information:

The Attempt to connect to the report server failed. Check your connection information and that the report server is a compatible version. (Microsoft.ReportingServices.Designer)

The status of all of my things in Reporting Services Configuration is Green and i can see my site in the IIS, i can also browse my site, it just doesn't want2 deploy.

Please HELP!!!

I suspect the problem lies here:

>I'm running a SQL 2000 DB with reporting Services 2005 and Visual Studio 2005

and, considering the error:

>that the report server is a compatible version

I am thinking there is a problem with your deploying RS 2005 reports to a 2000 RS database. I wasn't aware you could deploy 2005 reports to a 2000 RS database. Maybe you can do it if you don't convert (existing 2000) reports, I am not sure; but I doubt you'll be able to deploy them if you have converted them from 2000 to 2005. I especially think and new reports will bomb out since they would be native 2005.

There are threads in this forum that talk about this subject.

|||Try deploying to http://forge/reportserver instead.|||wow. good eye!|||

Thanks for th information but it still gives me the same error, but don't worry too much about it, i'm just going to reinstall SQL 2000 RS with Visual Studio 2003. apparently there is some incompatibility issue between .Net Framework 2.0 and 1.1 that prevent my solutions from working properly, so until i figure out the exact problem and link the Frameworks manually in my solution i doubt that it will work.

Thanks a lot for your effort guys!

|||

Hi

I traced down my problem, but i'll post my solution here just incase some else might battle with the same problem.

When i installed the RS i changed the Virtual Directory Name to Forge too, so when i deployed them i had to deploy them to Forge/Forge instead of Forge/ReportServer which it suppose to be by default. ->PC Name / ReportServer Virtual Directory<--

Error when i try to Deploy my reports to Reporting services - PLEASE HELP i'm also NEW at t

Hi

I'm running a SQL 2000 DB with reporting Services 2005 and Visual Studio 2005, I can connect and browse to Reporting Services through any management console and even to my site through //ServerName/Reports but when i try to deploy any of my reports to the Reporting Services through my VS2005 solution i get this error

A connection could not be made to the report server http://Forge/Reports.

Additional Information:

The Attempt to connect to the report server failed. Check your connection information and that the report server is a compatible version. (Microsoft.ReportingServices.Designer)

The status of all of my things in Reporting Services Configuration is Green and i can see my site in the IIS, i can also browse my site, it just doesn't want2 deploy.

Please HELP!!!

I suspect the problem lies here:

>I'm running a SQL 2000 DB with reporting Services 2005 and Visual Studio 2005

and, considering the error:

>that the report server is a compatible version

I am thinking there is a problem with your deploying RS 2005 reports to a 2000 RS database. I wasn't aware you could deploy 2005 reports to a 2000 RS database. Maybe you can do it if you don't convert (existing 2000) reports, I am not sure; but I doubt you'll be able to deploy them if you have converted them from 2000 to 2005. I especially think and new reports will bomb out since they would be native 2005.

There are threads in this forum that talk about this subject.

|||Try deploying to http://forge/reportserver instead.|||wow. good eye!|||

Thanks for th information but it still gives me the same error, but don't worry too much about it, i'm just going to reinstall SQL 2000 RS with Visual Studio 2003. apparently there is some incompatibility issue between .Net Framework 2.0 and 1.1 that prevent my solutions from working properly, so until i figure out the exact problem and link the Frameworks manually in my solution i doubt that it will work.

Thanks a lot for your effort guys!

|||

Hi

I traced down my problem, but i'll post my solution here just incase some else might battle with the same problem.

When i installed the RS i changed the Virtual Directory Name to Forge too, so when i deployed them i had to deploy them to Forge/Forge instead of Forge/ReportServer which it suppose to be by default. ->PC Name / ReportServer Virtual Directory<--

Error when connecting to SQLExpress

I have an issue that is totally baffling me. When I use a program I've
written to connect to SQLExpress (and a given database), all works well on
my development system and on a laptop that I tested with. However, I have
two users that I sent the SAME database files and program files to and at
the moment the program tries to connect to the server/database, they get the
generic Windows error message "[Your Program] has encountered an error and
needs to close. We are sorry for the inconvenience."
This differs from handled exceptions and unhandled exceptions within the
program. I have had the users uninstall their older SQLExpress and update to
the recent service pack, checked various configuration settings, including
owner of the database, including allowed remote connections, both TCP/IP and
NamedPipe. Everything "looks" correct, but no connection and the
above-mentioned Windows error message. I am just stumped, so I'd love to
hear any ideas or advice from anyone who has seen this before.
Let's hear a bit more about your configuration. I assume you're expecting an
existing SQL Express instance on the client system. Is it running? How are
the clients authenticated? I assume you have a Try/Catch around the Open.
Does the exception occur there? Is there a number with the error message?
Did you check the client systems event log? Let's see the ConnectionString.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"Earl" <brikshoe@.newsgroups.nospam> wrote in message
news:uHqd6%230LHHA.2232@.TK2MSFTNGP02.phx.gbl...
>I have an issue that is totally baffling me. When I use a program I've
>written to connect to SQLExpress (and a given database), all works well on
>my development system and on a laptop that I tested with. However, I have
>two users that I sent the SAME database files and program files to and at
>the moment the program tries to connect to the server/database, they get
>the generic Windows error message "[Your Program] has encountered an error
>and needs to close. We are sorry for the inconvenience."
> This differs from handled exceptions and unhandled exceptions within the
> program. I have had the users uninstall their older SQLExpress and update
> to the recent service pack, checked various configuration settings,
> including owner of the database, including allowed remote connections,
> both TCP/IP and NamedPipe. Everything "looks" correct, but no connection
> and the above-mentioned Windows error message. I am just stumped, so I'd
> love to hear any ideas or advice from anyone who has seen this before.
>
|||1. Yes, an existing SQL Express instance (I even tested it myself with
GotoMeeting, so I can see what they have)
2. It is running
3. Windows Authentication
4. Errors -- that is where the weirdness appears -- my error messages in the
Try/Catch do not show, I get the fancy generic Windows program error message
("We are sorry for the inconvenience..." the one where they want you to send
information to Microsoft).
5. I did not check the event log that is something I can review.
6. Connection string:
m_strConnection = "data source=" + m_strSQLServerName + ";" +
"initial catalog="+m_strDatabaseName+";integrated
security=SSPI;";
"William (Bill) Vaughn" <billvaRemoveThis@.nwlink.com> wrote in message
news:eZi8YW2LHHA.3668@.TK2MSFTNGP02.phx.gbl...
> Let's hear a bit more about your configuration. I assume you're expecting
> an existing SQL Express instance on the client system. Is it running? How
> are the clients authenticated? I assume you have a Try/Catch around the
> Open. Does the exception occur there? Is there a number with the error
> message? Did you check the client systems event log? Let's see the
> ConnectionString.
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ------
> "Earl" <brikshoe@.newsgroups.nospam> wrote in message
> news:uHqd6%230LHHA.2232@.TK2MSFTNGP02.phx.gbl...
>
|||Assuming you're trapping the "Exception" (generic catch-all) exception...
Ok. By default, SQL Server Express does not expose itself on the network. In
addition, it's generally installed as a named instance--usually "SQLEXPRESS"
so the strSQLServerName must include the instance name as in
MySystem\SQLEXPRESS
to reference it. You also need to have rights on the specified database
unless the current user is in the Admin group. You aren't using the User
Instance option which has its benefits and issues.
hth
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"Earl" <brikshoe@.newsgroups.nospam> wrote in message
news:uU42Ls3LHHA.140@.TK2MSFTNGP04.phx.gbl...
> 1. Yes, an existing SQL Express instance (I even tested it myself with
> GotoMeeting, so I can see what they have)
> 2. It is running
> 3. Windows Authentication
> 4. Errors -- that is where the weirdness appears -- my error messages in
> the Try/Catch do not show, I get the fancy generic Windows program error
> message ("We are sorry for the inconvenience..." the one where they want
> you to send information to Microsoft).
> 5. I did not check the event log that is something I can review.
> 6. Connection string:
> m_strConnection = "data source=" + m_strSQLServerName + ";" +
> "initial catalog="+m_strDatabaseName+";integrated
> security=SSPI;";
> "William (Bill) Vaughn" <billvaRemoveThis@.nwlink.com> wrote in message
> news:eZi8YW2LHHA.3668@.TK2MSFTNGP02.phx.gbl...
>
|||If anyone is still following this thread ... I've had the same response on 3
different systems now, one was a brand new install -- XP Pro, service pack
2, .Net 2.0 framework, SQLExpress2.0, and SSMSEE. I made no configuration
changes and accepted all defaults on the SQLExpress install, except for one:
I added the install user to the Administrator role.
Checked the event log after the crashes. The errors are showing as ".Net
Runtime 2.0 Errors". One error showed as "system.invalidoperationexception",
but all the others showed as "system.io.filenotfoundexception". Any
thoughts?
"William (Bill) Vaughn" <billvaRemoveThis@.nwlink.com> wrote in message
news:eLmTomGMHHA.1872@.TK2MSFTNGP04.phx.gbl...
> Assuming you're trapping the "Exception" (generic catch-all) exception...
> Ok. By default, SQL Server Express does not expose itself on the network.
> In addition, it's generally installed as a named instance--usually
> "SQLEXPRESS" so the strSQLServerName must include the instance name as in
> MySystem\SQLEXPRESS
> to reference it. You also need to have rights on the specified database
> unless the current user is in the Admin group. You aren't using the User
> Instance option which has its benefits and issues.
> hth
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ------
> "Earl" <brikshoe@.newsgroups.nospam> wrote in message
> news:uU42Ls3LHHA.140@.TK2MSFTNGP04.phx.gbl...
>
|||The one thing that seems to stand out to me is that you have never mentioned
any error or message coming from SQL Express. A file not found error from
the .Net framework seems to be unrelated to the database. You seem
convinced that this is a database error but you haven't given any evidence
of this. Have you debugged through the application startup to see where the
exception is thrown?
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Earl" <brikshoe@.newsgroups.nospam> wrote in message
news:uq26gHzMHHA.1240@.TK2MSFTNGP03.phx.gbl...
> If anyone is still following this thread ... I've had the same response on
> 3 different systems now, one was a brand new install -- XP Pro, service
> pack 2, .Net 2.0 framework, SQLExpress2.0, and SSMSEE. I made no
> configuration changes and accepted all defaults on the SQLExpress install,
> except for one: I added the install user to the Administrator role.
> Checked the event log after the crashes. The errors are showing as ".Net
> Runtime 2.0 Errors". One error showed as
> "system.invalidoperationexception", but all the others showed as
> "system.io.filenotfoundexception". Any thoughts?
>
> "William (Bill) Vaughn" <billvaRemoveThis@.nwlink.com> wrote in message
> news:eLmTomGMHHA.1872@.TK2MSFTNGP04.phx.gbl...
>
|||As I said, I am computer illiterate. SQL Express means nothing to me. I am
trying to make copies off of Adobe Reader and the generic screen you
mentioned pops up.
HHH
"Earl" wrote:

> I have an issue that is totally baffling me. When I use a program I've
> written to connect to SQLExpress (and a given database), all works well on
> my development system and on a laptop that I tested with. However, I have
> two users that I sent the SAME database files and program files to and at
> the moment the program tries to connect to the server/database, they get the
> generic Windows error message "[Your Program] has encountered an error and
> needs to close. We are sorry for the inconvenience."
> This differs from handled exceptions and unhandled exceptions within the
> program. I have had the users uninstall their older SQLExpress and update to
> the recent service pack, checked various configuration settings, including
> owner of the database, including allowed remote connections, both TCP/IP and
> NamedPipe. Everything "looks" correct, but no connection and the
> above-mentioned Windows error message. I am just stumped, so I'd love to
> hear any ideas or advice from anyone who has seen this before.
>
>
|||HHH
"Earl" wrote:

> I have an issue that is totally baffling me. When I use a program I've
> written to connect to SQLExpress (and a given database), all works well on
> my development system and on a laptop that I tested with. However, I have
> two users that I sent the SAME database files and program files to and at
> the moment the program tries to connect to the server/database, they get the
> generic Windows error message "[Your Program] has encountered an error and
> needs to close. We are sorry for the inconvenience."
> This differs from handled exceptions and unhandled exceptions within the
> program. I have had the users uninstall their older SQLExpress and update to
> the recent service pack, checked various configuration settings, including
> owner of the database, including allowed remote connections, both TCP/IP and
> NamedPipe. Everything "looks" correct, but no connection and the
> above-mentioned Windows error message. I am just stumped, so I'd love to
> hear any ideas or advice from anyone who has seen this before.
>
>
|||Actually, I did find the error in the app startup. It was a 3rd-party
component missing references.
"Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
news:%23oqf0ZzMHHA.1252@.TK2MSFTNGP02.phx.gbl...
> The one thing that seems to stand out to me is that you have never
> mentioned any error or message coming from SQL Express. A file not found
> error from the .Net framework seems to be unrelated to the database. You
> seem convinced that this is a database error but you haven't given any
> evidence of this. Have you debugged through the application startup to
> see where the exception is thrown?
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Earl" <brikshoe@.newsgroups.nospam> wrote in message
> news:uq26gHzMHHA.1240@.TK2MSFTNGP03.phx.gbl...
>

Error when connecting to SQLExpress

I have an issue that is totally baffling me. When I use a program I've
written to connect to SQLExpress (and a given database), all works well on
my development system and on a laptop that I tested with. However, I have
two users that I sent the SAME database files and program files to and at
the moment the program tries to connect to the server/database, they get the
generic Windows error message "[Your Program] has encountered an error a
nd
needs to close. We are sorry for the inconvenience."
This differs from handled exceptions and unhandled exceptions within the
program. I have had the users uninstall their older SQLExpress and update to
the recent service pack, checked various configuration settings, including
owner of the database, including allowed remote connections, both TCP/IP and
NamedPipe. Everything "looks" correct, but no connection and the
above-mentioned Windows error message. I am just stumped, so I'd love to
hear any ideas or advice from anyone who has seen this before.Let's hear a bit more about your configuration. I assume you're expecting an
existing SQL Express instance on the client system. Is it running? How are
the clients authenticated? I assume you have a Try/Catch around the Open.
Does the exception occur there? Is there a number with the error message?
Did you check the client systems event log? Let's see the ConnectionString.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
----
---
"Earl" <brikshoe@.newsgroups.nospam> wrote in message
news:uHqd6%230LHHA.2232@.TK2MSFTNGP02.phx.gbl...
>I have an issue that is totally baffling me. When I use a program I've
>written to connect to SQLExpress (and a given database), all works well on
>my development system and on a laptop that I tested with. However, I have
>two users that I sent the SAME database files and program files to and at
>the moment the program tries to connect to the server/database, they get
>the generic Windows error message "[Your Program] has encountered an er
ror
>and needs to close. We are sorry for the inconvenience."
> This differs from handled exceptions and unhandled exceptions within the
> program. I have had the users uninstall their older SQLExpress and update
> to the recent service pack, checked various configuration settings,
> including owner of the database, including allowed remote connections,
> both TCP/IP and NamedPipe. Everything "looks" correct, but no connection
> and the above-mentioned Windows error message. I am just stumped, so I'd
> love to hear any ideas or advice from anyone who has seen this before.
>|||1. Yes, an existing SQL Express instance (I even tested it myself with
GotoMeeting, so I can see what they have)
2. It is running
3. Windows Authentication
4. Errors -- that is where the weirdness appears -- my error messages in the
Try/Catch do not show, I get the fancy generic Windows program error message
("We are sorry for the inconvenience..." the one where they want you to send
information to Microsoft).
5. I did not check the event log that is something I can review.
6. Connection string:
m_strConnection = "data source=" + m_strSQLServerName + ";" +
"initial catalog="+m_strDatabaseName+";integrated
security=SSPI;";
"William (Bill) Vaughn" <billvaRemoveThis@.nwlink.com> wrote in message
news:eZi8YW2LHHA.3668@.TK2MSFTNGP02.phx.gbl...
> Let's hear a bit more about your configuration. I assume you're expecting
> an existing SQL Express instance on the client system. Is it running? How
> are the clients authenticated? I assume you have a Try/Catch around the
> Open. Does the exception occur there? Is there a number with the error
> message? Did you check the client systems event log? Let's see the
> ConnectionString.
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ----
---
> "Earl" <brikshoe@.newsgroups.nospam> wrote in message
> news:uHqd6%230LHHA.2232@.TK2MSFTNGP02.phx.gbl...
>|||Assuming you're trapping the "Exception" (generic catch-all) exception...
Ok. By default, SQL Server Express does not expose itself on the network. In
addition, it's generally installed as a named instance--usually "SQLEXPRESS"
so the strSQLServerName must include the instance name as in
MySystem\SQLEXPRESS
to reference it. You also need to have rights on the specified database
unless the current user is in the Admin group. You aren't using the User
Instance option which has its benefits and issues.
hth
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
----
---
"Earl" <brikshoe@.newsgroups.nospam> wrote in message
news:uU42Ls3LHHA.140@.TK2MSFTNGP04.phx.gbl...
> 1. Yes, an existing SQL Express instance (I even tested it myself with
> GotoMeeting, so I can see what they have)
> 2. It is running
> 3. Windows Authentication
> 4. Errors -- that is where the weirdness appears -- my error messages in
> the Try/Catch do not show, I get the fancy generic Windows program error
> message ("We are sorry for the inconvenience..." the one where they want
> you to send information to Microsoft).
> 5. I did not check the event log that is something I can review.
> 6. Connection string:
> m_strConnection = "data source=" + m_strSQLServerName + ";" +
> "initial catalog="+m_strDatabaseName+";integrated
> security=SSPI;";
> "William (Bill) Vaughn" <billvaRemoveThis@.nwlink.com> wrote in message
> news:eZi8YW2LHHA.3668@.TK2MSFTNGP02.phx.gbl...
>|||If anyone is still following this thread ... I've had the same response on 3
different systems now, one was a brand new install -- XP Pro, service pack
2, .Net 2.0 framework, SQLExpress2.0, and SSMSEE. I made no configuration
changes and accepted all defaults on the SQLExpress install, except for one:
I added the install user to the Administrator role.
Checked the event log after the crashes. The errors are showing as ".Net
Runtime 2.0 Errors". One error showed as "system.invalidoperationexception",
but all the others showed as "system.io.filenotfoundexception". Any
thoughts?
"William (Bill) Vaughn" <billvaRemoveThis@.nwlink.com> wrote in message
news:eLmTomGMHHA.1872@.TK2MSFTNGP04.phx.gbl...
> Assuming you're trapping the "Exception" (generic catch-all) exception...
> Ok. By default, SQL Server Express does not expose itself on the network.
> In addition, it's generally installed as a named instance--usually
> "SQLEXPRESS" so the strSQLServerName must include the instance name as in
> MySystem\SQLEXPRESS
> to reference it. You also need to have rights on the specified database
> unless the current user is in the Admin group. You aren't using the User
> Instance option which has its benefits and issues.
> hth
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ----
---
> "Earl" <brikshoe@.newsgroups.nospam> wrote in message
> news:uU42Ls3LHHA.140@.TK2MSFTNGP04.phx.gbl...
>|||The one thing that seems to stand out to me is that you have never mentioned
any error or message coming from SQL Express. A file not found error from
the .Net framework seems to be unrelated to the database. You seem
convinced that this is a database error but you haven't given any evidence
of this. Have you debugged through the application startup to see where the
exception is thrown?
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Earl" <brikshoe@.newsgroups.nospam> wrote in message
news:uq26gHzMHHA.1240@.TK2MSFTNGP03.phx.gbl...
> If anyone is still following this thread ... I've had the same response on
> 3 different systems now, one was a brand new install -- XP Pro, service
> pack 2, .Net 2.0 framework, SQLExpress2.0, and SSMSEE. I made no
> configuration changes and accepted all defaults on the SQLExpress install,
> except for one: I added the install user to the Administrator role.
> Checked the event log after the crashes. The errors are showing as ".Net
> Runtime 2.0 Errors". One error showed as
> "system.invalidoperationexception", but all the others showed as
> "system.io.filenotfoundexception". Any thoughts?
>
> "William (Bill) Vaughn" <billvaRemoveThis@.nwlink.com> wrote in message
> news:eLmTomGMHHA.1872@.TK2MSFTNGP04.phx.gbl...
>|||As I said, I am computer illiterate. SQL Express means nothing to me. I am
trying to make copies off of Adobe Reader and the generic screen you
mentioned pops up.
--
HHH
"Earl" wrote:

> I have an issue that is totally baffling me. When I use a program I've
> written to connect to SQLExpress (and a given database), all works well on
> my development system and on a laptop that I tested with. However, I have
> two users that I sent the SAME database files and program files to and at
> the moment the program tries to connect to the server/database, they get t
he
> generic Windows error message "[Your Program] has encountered an error
and
> needs to close. We are sorry for the inconvenience."
> This differs from handled exceptions and unhandled exceptions within the
> program. I have had the users uninstall their older SQLExpress and update
to
> the recent service pack, checked various configuration settings, including
> owner of the database, including allowed remote connections, both TCP/IP a
nd
> NamedPipe. Everything "looks" correct, but no connection and the
> above-mentioned Windows error message. I am just stumped, so I'd love to
> hear any ideas or advice from anyone who has seen this before.
>
>|||HHH
"Earl" wrote:

> I have an issue that is totally baffling me. When I use a program I've
> written to connect to SQLExpress (and a given database), all works well on
> my development system and on a laptop that I tested with. However, I have
> two users that I sent the SAME database files and program files to and at
> the moment the program tries to connect to the server/database, they get t
he
> generic Windows error message "[Your Program] has encountered an error
and
> needs to close. We are sorry for the inconvenience."
> This differs from handled exceptions and unhandled exceptions within the
> program. I have had the users uninstall their older SQLExpress and update
to
> the recent service pack, checked various configuration settings, including
> owner of the database, including allowed remote connections, both TCP/IP a
nd
> NamedPipe. Everything "looks" correct, but no connection and the
> above-mentioned Windows error message. I am just stumped, so I'd love to
> hear any ideas or advice from anyone who has seen this before.
>
>|||Actually, I did find the error in the app startup. It was a 3rd-party
component missing references.
"Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
news:%23oqf0ZzMHHA.1252@.TK2MSFTNGP02.phx.gbl...
> The one thing that seems to stand out to me is that you have never
> mentioned any error or message coming from SQL Express. A file not found
> error from the .Net framework seems to be unrelated to the database. You
> seem convinced that this is a database error but you haven't given any
> evidence of this. Have you debugged through the application startup to
> see where the exception is thrown?
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Earl" <brikshoe@.newsgroups.nospam> wrote in message
> news:uq26gHzMHHA.1240@.TK2MSFTNGP03.phx.gbl...
>

Error when connecting to SQLExpress

I have an issue that is totally baffling me. When I use a program I've
written to connect to SQLExpress (and a given database), all works well on
my development system and on a laptop that I tested with. However, I have
two users that I sent the SAME database files and program files to and at
the moment the program tries to connect to the server/database, they get the
generic Windows error message "[Your Program] has encountered an error and
needs to close. We are sorry for the inconvenience."
This differs from handled exceptions and unhandled exceptions within the
program. I have had the users uninstall their older SQLExpress and update to
the recent service pack, checked various configuration settings, including
owner of the database, including allowed remote connections, both TCP/IP and
NamedPipe. Everything "looks" correct, but no connection and the
above-mentioned Windows error message. I am just stumped, so I'd love to
hear any ideas or advice from anyone who has seen this before.
Let's hear a bit more about your configuration. I assume you're expecting an
existing SQL Express instance on the client system. Is it running? How are
the clients authenticated? I assume you have a Try/Catch around the Open.
Does the exception occur there? Is there a number with the error message?
Did you check the client systems event log? Let's see the ConnectionString.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"Earl" <brikshoe@.newsgroups.nospam> wrote in message
news:uHqd6%230LHHA.2232@.TK2MSFTNGP02.phx.gbl...
>I have an issue that is totally baffling me. When I use a program I've
>written to connect to SQLExpress (and a given database), all works well on
>my development system and on a laptop that I tested with. However, I have
>two users that I sent the SAME database files and program files to and at
>the moment the program tries to connect to the server/database, they get
>the generic Windows error message "[Your Program] has encountered an error
>and needs to close. We are sorry for the inconvenience."
> This differs from handled exceptions and unhandled exceptions within the
> program. I have had the users uninstall their older SQLExpress and update
> to the recent service pack, checked various configuration settings,
> including owner of the database, including allowed remote connections,
> both TCP/IP and NamedPipe. Everything "looks" correct, but no connection
> and the above-mentioned Windows error message. I am just stumped, so I'd
> love to hear any ideas or advice from anyone who has seen this before.
>
|||1. Yes, an existing SQL Express instance (I even tested it myself with
GotoMeeting, so I can see what they have)
2. It is running
3. Windows Authentication
4. Errors -- that is where the weirdness appears -- my error messages in the
Try/Catch do not show, I get the fancy generic Windows program error message
("We are sorry for the inconvenience..." the one where they want you to send
information to Microsoft).
5. I did not check the event log that is something I can review.
6. Connection string:
m_strConnection = "data source=" + m_strSQLServerName + ";" +
"initial catalog="+m_strDatabaseName+";integrated
security=SSPI;";
"William (Bill) Vaughn" <billvaRemoveThis@.nwlink.com> wrote in message
news:eZi8YW2LHHA.3668@.TK2MSFTNGP02.phx.gbl...
> Let's hear a bit more about your configuration. I assume you're expecting
> an existing SQL Express instance on the client system. Is it running? How
> are the clients authenticated? I assume you have a Try/Catch around the
> Open. Does the exception occur there? Is there a number with the error
> message? Did you check the client systems event log? Let's see the
> ConnectionString.
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ------
> "Earl" <brikshoe@.newsgroups.nospam> wrote in message
> news:uHqd6%230LHHA.2232@.TK2MSFTNGP02.phx.gbl...
>
|||Assuming you're trapping the "Exception" (generic catch-all) exception...
Ok. By default, SQL Server Express does not expose itself on the network. In
addition, it's generally installed as a named instance--usually "SQLEXPRESS"
so the strSQLServerName must include the instance name as in
MySystem\SQLEXPRESS
to reference it. You also need to have rights on the specified database
unless the current user is in the Admin group. You aren't using the User
Instance option which has its benefits and issues.
hth
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"Earl" <brikshoe@.newsgroups.nospam> wrote in message
news:uU42Ls3LHHA.140@.TK2MSFTNGP04.phx.gbl...
> 1. Yes, an existing SQL Express instance (I even tested it myself with
> GotoMeeting, so I can see what they have)
> 2. It is running
> 3. Windows Authentication
> 4. Errors -- that is where the weirdness appears -- my error messages in
> the Try/Catch do not show, I get the fancy generic Windows program error
> message ("We are sorry for the inconvenience..." the one where they want
> you to send information to Microsoft).
> 5. I did not check the event log that is something I can review.
> 6. Connection string:
> m_strConnection = "data source=" + m_strSQLServerName + ";" +
> "initial catalog="+m_strDatabaseName+";integrated
> security=SSPI;";
> "William (Bill) Vaughn" <billvaRemoveThis@.nwlink.com> wrote in message
> news:eZi8YW2LHHA.3668@.TK2MSFTNGP02.phx.gbl...
>
|||If anyone is still following this thread ... I've had the same response on 3
different systems now, one was a brand new install -- XP Pro, service pack
2, .Net 2.0 framework, SQLExpress2.0, and SSMSEE. I made no configuration
changes and accepted all defaults on the SQLExpress install, except for one:
I added the install user to the Administrator role.
Checked the event log after the crashes. The errors are showing as ".Net
Runtime 2.0 Errors". One error showed as "system.invalidoperationexception",
but all the others showed as "system.io.filenotfoundexception". Any
thoughts?
"William (Bill) Vaughn" <billvaRemoveThis@.nwlink.com> wrote in message
news:eLmTomGMHHA.1872@.TK2MSFTNGP04.phx.gbl...
> Assuming you're trapping the "Exception" (generic catch-all) exception...
> Ok. By default, SQL Server Express does not expose itself on the network.
> In addition, it's generally installed as a named instance--usually
> "SQLEXPRESS" so the strSQLServerName must include the instance name as in
> MySystem\SQLEXPRESS
> to reference it. You also need to have rights on the specified database
> unless the current user is in the Admin group. You aren't using the User
> Instance option which has its benefits and issues.
> hth
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ------
> "Earl" <brikshoe@.newsgroups.nospam> wrote in message
> news:uU42Ls3LHHA.140@.TK2MSFTNGP04.phx.gbl...
>
|||The one thing that seems to stand out to me is that you have never mentioned
any error or message coming from SQL Express. A file not found error from
the .Net framework seems to be unrelated to the database. You seem
convinced that this is a database error but you haven't given any evidence
of this. Have you debugged through the application startup to see where the
exception is thrown?
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Earl" <brikshoe@.newsgroups.nospam> wrote in message
news:uq26gHzMHHA.1240@.TK2MSFTNGP03.phx.gbl...
> If anyone is still following this thread ... I've had the same response on
> 3 different systems now, one was a brand new install -- XP Pro, service
> pack 2, .Net 2.0 framework, SQLExpress2.0, and SSMSEE. I made no
> configuration changes and accepted all defaults on the SQLExpress install,
> except for one: I added the install user to the Administrator role.
> Checked the event log after the crashes. The errors are showing as ".Net
> Runtime 2.0 Errors". One error showed as
> "system.invalidoperationexception", but all the others showed as
> "system.io.filenotfoundexception". Any thoughts?
>
> "William (Bill) Vaughn" <billvaRemoveThis@.nwlink.com> wrote in message
> news:eLmTomGMHHA.1872@.TK2MSFTNGP04.phx.gbl...
>
|||As I said, I am computer illiterate. SQL Express means nothing to me. I am
trying to make copies off of Adobe Reader and the generic screen you
mentioned pops up.
HHH
"Earl" wrote:

> I have an issue that is totally baffling me. When I use a program I've
> written to connect to SQLExpress (and a given database), all works well on
> my development system and on a laptop that I tested with. However, I have
> two users that I sent the SAME database files and program files to and at
> the moment the program tries to connect to the server/database, they get the
> generic Windows error message "[Your Program] has encountered an error and
> needs to close. We are sorry for the inconvenience."
> This differs from handled exceptions and unhandled exceptions within the
> program. I have had the users uninstall their older SQLExpress and update to
> the recent service pack, checked various configuration settings, including
> owner of the database, including allowed remote connections, both TCP/IP and
> NamedPipe. Everything "looks" correct, but no connection and the
> above-mentioned Windows error message. I am just stumped, so I'd love to
> hear any ideas or advice from anyone who has seen this before.
>
>
|||HHH
"Earl" wrote:

> I have an issue that is totally baffling me. When I use a program I've
> written to connect to SQLExpress (and a given database), all works well on
> my development system and on a laptop that I tested with. However, I have
> two users that I sent the SAME database files and program files to and at
> the moment the program tries to connect to the server/database, they get the
> generic Windows error message "[Your Program] has encountered an error and
> needs to close. We are sorry for the inconvenience."
> This differs from handled exceptions and unhandled exceptions within the
> program. I have had the users uninstall their older SQLExpress and update to
> the recent service pack, checked various configuration settings, including
> owner of the database, including allowed remote connections, both TCP/IP and
> NamedPipe. Everything "looks" correct, but no connection and the
> above-mentioned Windows error message. I am just stumped, so I'd love to
> hear any ideas or advice from anyone who has seen this before.
>
>
|||Actually, I did find the error in the app startup. It was a 3rd-party
component missing references.
"Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
news:%23oqf0ZzMHHA.1252@.TK2MSFTNGP02.phx.gbl...
> The one thing that seems to stand out to me is that you have never
> mentioned any error or message coming from SQL Express. A file not found
> error from the .Net framework seems to be unrelated to the database. You
> seem convinced that this is a database error but you haven't given any
> evidence of this. Have you debugged through the application startup to
> see where the exception is thrown?
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Earl" <brikshoe@.newsgroups.nospam> wrote in message
> news:uq26gHzMHHA.1240@.TK2MSFTNGP03.phx.gbl...
>

Error when connecting to SQLExpress

I have an issue that is totally baffling me. When I use a program I've
written to connect to SQLExpress (and a given database), all works well on
my development system and on a laptop that I tested with. However, I have
two users that I sent the SAME database files and program files to and at
the moment the program tries to connect to the server/database, they get the
generic Windows error message "[Your Program] has encountered an error and
needs to close. We are sorry for the inconvenience."
This differs from handled exceptions and unhandled exceptions within the
program. I have had the users uninstall their older SQLExpress and update to
the recent service pack, checked various configuration settings, including
owner of the database, including allowed remote connections, both TCP/IP and
NamedPipe. Everything "looks" correct, but no connection and the
above-mentioned Windows error message. I am just stumped, so I'd love to
hear any ideas or advice from anyone who has seen this before.Let's hear a bit more about your configuration. I assume you're expecting an
existing SQL Express instance on the client system. Is it running? How are
the clients authenticated? I assume you have a Try/Catch around the Open.
Does the exception occur there? Is there a number with the error message?
Did you check the client systems event log? Let's see the ConnectionString.
--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"Earl" <brikshoe@.newsgroups.nospam> wrote in message
news:uHqd6%230LHHA.2232@.TK2MSFTNGP02.phx.gbl...
>I have an issue that is totally baffling me. When I use a program I've
>written to connect to SQLExpress (and a given database), all works well on
>my development system and on a laptop that I tested with. However, I have
>two users that I sent the SAME database files and program files to and at
>the moment the program tries to connect to the server/database, they get
>the generic Windows error message "[Your Program] has encountered an error
>and needs to close. We are sorry for the inconvenience."
> This differs from handled exceptions and unhandled exceptions within the
> program. I have had the users uninstall their older SQLExpress and update
> to the recent service pack, checked various configuration settings,
> including owner of the database, including allowed remote connections,
> both TCP/IP and NamedPipe. Everything "looks" correct, but no connection
> and the above-mentioned Windows error message. I am just stumped, so I'd
> love to hear any ideas or advice from anyone who has seen this before.
>|||1. Yes, an existing SQL Express instance (I even tested it myself with
GotoMeeting, so I can see what they have)
2. It is running
3. Windows Authentication
4. Errors -- that is where the weirdness appears -- my error messages in the
Try/Catch do not show, I get the fancy generic Windows program error message
("We are sorry for the inconvenience..." the one where they want you to send
information to Microsoft).
5. I did not check the event log that is something I can review.
6. Connection string:
m_strConnection = "data source=" + m_strSQLServerName + ";" +
"initial catalog="+m_strDatabaseName+";integrated
security=SSPI;";
"William (Bill) Vaughn" <billvaRemoveThis@.nwlink.com> wrote in message
news:eZi8YW2LHHA.3668@.TK2MSFTNGP02.phx.gbl...
> Let's hear a bit more about your configuration. I assume you're expecting
> an existing SQL Express instance on the client system. Is it running? How
> are the clients authenticated? I assume you have a Try/Catch around the
> Open. Does the exception occur there? Is there a number with the error
> message? Did you check the client systems event log? Let's see the
> ConnectionString.
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ------
> "Earl" <brikshoe@.newsgroups.nospam> wrote in message
> news:uHqd6%230LHHA.2232@.TK2MSFTNGP02.phx.gbl...
>>I have an issue that is totally baffling me. When I use a program I've
>>written to connect to SQLExpress (and a given database), all works well on
>>my development system and on a laptop that I tested with. However, I have
>>two users that I sent the SAME database files and program files to and at
>>the moment the program tries to connect to the server/database, they get
>>the generic Windows error message "[Your Program] has encountered an error
>>and needs to close. We are sorry for the inconvenience."
>> This differs from handled exceptions and unhandled exceptions within the
>> program. I have had the users uninstall their older SQLExpress and update
>> to the recent service pack, checked various configuration settings,
>> including owner of the database, including allowed remote connections,
>> both TCP/IP and NamedPipe. Everything "looks" correct, but no connection
>> and the above-mentioned Windows error message. I am just stumped, so I'd
>> love to hear any ideas or advice from anyone who has seen this before.
>|||Assuming you're trapping the "Exception" (generic catch-all) exception...
Ok. By default, SQL Server Express does not expose itself on the network. In
addition, it's generally installed as a named instance--usually "SQLEXPRESS"
so the strSQLServerName must include the instance name as in
MySystem\SQLEXPRESS
to reference it. You also need to have rights on the specified database
unless the current user is in the Admin group. You aren't using the User
Instance option which has its benefits and issues.
hth
--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"Earl" <brikshoe@.newsgroups.nospam> wrote in message
news:uU42Ls3LHHA.140@.TK2MSFTNGP04.phx.gbl...
> 1. Yes, an existing SQL Express instance (I even tested it myself with
> GotoMeeting, so I can see what they have)
> 2. It is running
> 3. Windows Authentication
> 4. Errors -- that is where the weirdness appears -- my error messages in
> the Try/Catch do not show, I get the fancy generic Windows program error
> message ("We are sorry for the inconvenience..." the one where they want
> you to send information to Microsoft).
> 5. I did not check the event log that is something I can review.
> 6. Connection string:
> m_strConnection = "data source=" + m_strSQLServerName + ";" +
> "initial catalog="+m_strDatabaseName+";integrated
> security=SSPI;";
> "William (Bill) Vaughn" <billvaRemoveThis@.nwlink.com> wrote in message
> news:eZi8YW2LHHA.3668@.TK2MSFTNGP02.phx.gbl...
>> Let's hear a bit more about your configuration. I assume you're expecting
>> an existing SQL Express instance on the client system. Is it running? How
>> are the clients authenticated? I assume you have a Try/Catch around the
>> Open. Does the exception occur there? Is there a number with the error
>> message? Did you check the client systems event log? Let's see the
>> ConnectionString.
>> --
>> ____________________________________
>> William (Bill) Vaughn
>> Author, Mentor, Consultant
>> Microsoft MVP
>> INETA Speaker
>> www.betav.com/blog/billva
>> www.betav.com
>> Please reply only to the newsgroup so that others can benefit.
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> __________________________________
>> Visit www.hitchhikerguides.net to get more information on my latest book:
>> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
>> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
>> ------
>> "Earl" <brikshoe@.newsgroups.nospam> wrote in message
>> news:uHqd6%230LHHA.2232@.TK2MSFTNGP02.phx.gbl...
>>I have an issue that is totally baffling me. When I use a program I've
>>written to connect to SQLExpress (and a given database), all works well
>>on my development system and on a laptop that I tested with. However, I
>>have two users that I sent the SAME database files and program files to
>>and at the moment the program tries to connect to the server/database,
>>they get the generic Windows error message "[Your Program] has
>>encountered an error and needs to close. We are sorry for the
>>inconvenience."
>> This differs from handled exceptions and unhandled exceptions within the
>> program. I have had the users uninstall their older SQLExpress and
>> update to the recent service pack, checked various configuration
>> settings, including owner of the database, including allowed remote
>> connections, both TCP/IP and NamedPipe. Everything "looks" correct, but
>> no connection and the above-mentioned Windows error message. I am just
>> stumped, so I'd love to hear any ideas or advice from anyone who has
>> seen this before.
>>
>|||If anyone is still following this thread ... I've had the same response on 3
different systems now, one was a brand new install -- XP Pro, service pack
2, .Net 2.0 framework, SQLExpress2.0, and SSMSEE. I made no configuration
changes and accepted all defaults on the SQLExpress install, except for one:
I added the install user to the Administrator role.
Checked the event log after the crashes. The errors are showing as ".Net
Runtime 2.0 Errors". One error showed as "system.invalidoperationexception",
but all the others showed as "system.io.filenotfoundexception". Any
thoughts?
"William (Bill) Vaughn" <billvaRemoveThis@.nwlink.com> wrote in message
news:eLmTomGMHHA.1872@.TK2MSFTNGP04.phx.gbl...
> Assuming you're trapping the "Exception" (generic catch-all) exception...
> Ok. By default, SQL Server Express does not expose itself on the network.
> In addition, it's generally installed as a named instance--usually
> "SQLEXPRESS" so the strSQLServerName must include the instance name as in
> MySystem\SQLEXPRESS
> to reference it. You also need to have rights on the specified database
> unless the current user is in the Admin group. You aren't using the User
> Instance option which has its benefits and issues.
> hth
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ------
> "Earl" <brikshoe@.newsgroups.nospam> wrote in message
> news:uU42Ls3LHHA.140@.TK2MSFTNGP04.phx.gbl...
>> 1. Yes, an existing SQL Express instance (I even tested it myself with
>> GotoMeeting, so I can see what they have)
>> 2. It is running
>> 3. Windows Authentication
>> 4. Errors -- that is where the weirdness appears -- my error messages in
>> the Try/Catch do not show, I get the fancy generic Windows program error
>> message ("We are sorry for the inconvenience..." the one where they want
>> you to send information to Microsoft).
>> 5. I did not check the event log that is something I can review.
>> 6. Connection string:
>> m_strConnection = "data source=" + m_strSQLServerName + ";" +
>> "initial catalog="+m_strDatabaseName+";integrated
>> security=SSPI;";
>> "William (Bill) Vaughn" <billvaRemoveThis@.nwlink.com> wrote in message
>> news:eZi8YW2LHHA.3668@.TK2MSFTNGP02.phx.gbl...
>> Let's hear a bit more about your configuration. I assume you're
>> expecting an existing SQL Express instance on the client system. Is it
>> running? How are the clients authenticated? I assume you have a
>> Try/Catch around the Open. Does the exception occur there? Is there a
>> number with the error message? Did you check the client systems event
>> log? Let's see the ConnectionString.
>> --
>> ____________________________________
>> William (Bill) Vaughn
>> Author, Mentor, Consultant
>> Microsoft MVP
>> INETA Speaker
>> www.betav.com/blog/billva
>> www.betav.com
>> Please reply only to the newsgroup so that others can benefit.
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> __________________________________
>> Visit www.hitchhikerguides.net to get more information on my latest
>> book:
>> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
>> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
>> ------
>> "Earl" <brikshoe@.newsgroups.nospam> wrote in message
>> news:uHqd6%230LHHA.2232@.TK2MSFTNGP02.phx.gbl...
>>I have an issue that is totally baffling me. When I use a program I've
>>written to connect to SQLExpress (and a given database), all works well
>>on my development system and on a laptop that I tested with. However, I
>>have two users that I sent the SAME database files and program files to
>>and at the moment the program tries to connect to the server/database,
>>they get the generic Windows error message "[Your Program] has
>>encountered an error and needs to close. We are sorry for the
>>inconvenience."
>> This differs from handled exceptions and unhandled exceptions within
>> the program. I have had the users uninstall their older SQLExpress and
>> update to the recent service pack, checked various configuration
>> settings, including owner of the database, including allowed remote
>> connections, both TCP/IP and NamedPipe. Everything "looks" correct, but
>> no connection and the above-mentioned Windows error message. I am just
>> stumped, so I'd love to hear any ideas or advice from anyone who has
>> seen this before.
>>
>>
>|||The one thing that seems to stand out to me is that you have never mentioned
any error or message coming from SQL Express. A file not found error from
the .Net framework seems to be unrelated to the database. You seem
convinced that this is a database error but you haven't given any evidence
of this. Have you debugged through the application startup to see where the
exception is thrown?
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Earl" <brikshoe@.newsgroups.nospam> wrote in message
news:uq26gHzMHHA.1240@.TK2MSFTNGP03.phx.gbl...
> If anyone is still following this thread ... I've had the same response on
> 3 different systems now, one was a brand new install -- XP Pro, service
> pack 2, .Net 2.0 framework, SQLExpress2.0, and SSMSEE. I made no
> configuration changes and accepted all defaults on the SQLExpress install,
> except for one: I added the install user to the Administrator role.
> Checked the event log after the crashes. The errors are showing as ".Net
> Runtime 2.0 Errors". One error showed as
> "system.invalidoperationexception", but all the others showed as
> "system.io.filenotfoundexception". Any thoughts?
>
> "William (Bill) Vaughn" <billvaRemoveThis@.nwlink.com> wrote in message
> news:eLmTomGMHHA.1872@.TK2MSFTNGP04.phx.gbl...
>> Assuming you're trapping the "Exception" (generic catch-all) exception...
>> Ok. By default, SQL Server Express does not expose itself on the network.
>> In addition, it's generally installed as a named instance--usually
>> "SQLEXPRESS" so the strSQLServerName must include the instance name as in
>> MySystem\SQLEXPRESS
>> to reference it. You also need to have rights on the specified database
>> unless the current user is in the Admin group. You aren't using the User
>> Instance option which has its benefits and issues.
>> hth
>> --
>> ____________________________________
>> William (Bill) Vaughn
>> Author, Mentor, Consultant
>> Microsoft MVP
>> INETA Speaker
>> www.betav.com/blog/billva
>> www.betav.com
>> Please reply only to the newsgroup so that others can benefit.
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> __________________________________
>> Visit www.hitchhikerguides.net to get more information on my latest book:
>> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
>> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
>> ------
>> "Earl" <brikshoe@.newsgroups.nospam> wrote in message
>> news:uU42Ls3LHHA.140@.TK2MSFTNGP04.phx.gbl...
>> 1. Yes, an existing SQL Express instance (I even tested it myself with
>> GotoMeeting, so I can see what they have)
>> 2. It is running
>> 3. Windows Authentication
>> 4. Errors -- that is where the weirdness appears -- my error messages in
>> the Try/Catch do not show, I get the fancy generic Windows program error
>> message ("We are sorry for the inconvenience..." the one where they want
>> you to send information to Microsoft).
>> 5. I did not check the event log that is something I can review.
>> 6. Connection string:
>> m_strConnection = "data source=" + m_strSQLServerName + ";" +
>> "initial catalog="+m_strDatabaseName+";integrated
>> security=SSPI;";
>> "William (Bill) Vaughn" <billvaRemoveThis@.nwlink.com> wrote in message
>> news:eZi8YW2LHHA.3668@.TK2MSFTNGP02.phx.gbl...
>> Let's hear a bit more about your configuration. I assume you're
>> expecting an existing SQL Express instance on the client system. Is it
>> running? How are the clients authenticated? I assume you have a
>> Try/Catch around the Open. Does the exception occur there? Is there a
>> number with the error message? Did you check the client systems event
>> log? Let's see the ConnectionString.
>> --
>> ____________________________________
>> William (Bill) Vaughn
>> Author, Mentor, Consultant
>> Microsoft MVP
>> INETA Speaker
>> www.betav.com/blog/billva
>> www.betav.com
>> Please reply only to the newsgroup so that others can benefit.
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> __________________________________
>> Visit www.hitchhikerguides.net to get more information on my latest
>> book:
>> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
>> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
>> ------
>> "Earl" <brikshoe@.newsgroups.nospam> wrote in message
>> news:uHqd6%230LHHA.2232@.TK2MSFTNGP02.phx.gbl...
>>I have an issue that is totally baffling me. When I use a program I've
>>written to connect to SQLExpress (and a given database), all works well
>>on my development system and on a laptop that I tested with. However, I
>>have two users that I sent the SAME database files and program files to
>>and at the moment the program tries to connect to the server/database,
>>they get the generic Windows error message "[Your Program] has
>>encountered an error and needs to close. We are sorry for the
>>inconvenience."
>> This differs from handled exceptions and unhandled exceptions within
>> the program. I have had the users uninstall their older SQLExpress and
>> update to the recent service pack, checked various configuration
>> settings, including owner of the database, including allowed remote
>> connections, both TCP/IP and NamedPipe. Everything "looks" correct,
>> but no connection and the above-mentioned Windows error message. I am
>> just stumped, so I'd love to hear any ideas or advice from anyone who
>> has seen this before.
>>
>>
>>
>|||Actually, I did find the error in the app startup. It was a 3rd-party
component missing references.
"Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
news:%23oqf0ZzMHHA.1252@.TK2MSFTNGP02.phx.gbl...
> The one thing that seems to stand out to me is that you have never
> mentioned any error or message coming from SQL Express. A file not found
> error from the .Net framework seems to be unrelated to the database. You
> seem convinced that this is a database error but you haven't given any
> evidence of this. Have you debugged through the application startup to
> see where the exception is thrown?
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Earl" <brikshoe@.newsgroups.nospam> wrote in message
> news:uq26gHzMHHA.1240@.TK2MSFTNGP03.phx.gbl...
>> If anyone is still following this thread ... I've had the same response
>> on 3 different systems now, one was a brand new install -- XP Pro,
>> service pack 2, .Net 2.0 framework, SQLExpress2.0, and SSMSEE. I made no
>> configuration changes and accepted all defaults on the SQLExpress
>> install, except for one: I added the install user to the Administrator
>> role.
>> Checked the event log after the crashes. The errors are showing as ".Net
>> Runtime 2.0 Errors". One error showed as
>> "system.invalidoperationexception", but all the others showed as
>> "system.io.filenotfoundexception". Any thoughts?
>>
>> "William (Bill) Vaughn" <billvaRemoveThis@.nwlink.com> wrote in message
>> news:eLmTomGMHHA.1872@.TK2MSFTNGP04.phx.gbl...
>> Assuming you're trapping the "Exception" (generic catch-all)
>> exception...
>> Ok. By default, SQL Server Express does not expose itself on the
>> network. In addition, it's generally installed as a named
>> instance--usually "SQLEXPRESS" so the strSQLServerName must include the
>> instance name as in
>> MySystem\SQLEXPRESS
>> to reference it. You also need to have rights on the specified database
>> unless the current user is in the Admin group. You aren't using the User
>> Instance option which has its benefits and issues.
>> hth
>> --
>> ____________________________________
>> William (Bill) Vaughn
>> Author, Mentor, Consultant
>> Microsoft MVP
>> INETA Speaker
>> www.betav.com/blog/billva
>> www.betav.com
>> Please reply only to the newsgroup so that others can benefit.
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> __________________________________
>> Visit www.hitchhikerguides.net to get more information on my latest
>> book:
>> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
>> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
>> ------
>> "Earl" <brikshoe@.newsgroups.nospam> wrote in message
>> news:uU42Ls3LHHA.140@.TK2MSFTNGP04.phx.gbl...
>> 1. Yes, an existing SQL Express instance (I even tested it myself with
>> GotoMeeting, so I can see what they have)
>> 2. It is running
>> 3. Windows Authentication
>> 4. Errors -- that is where the weirdness appears -- my error messages
>> in the Try/Catch do not show, I get the fancy generic Windows program
>> error message ("We are sorry for the inconvenience..." the one where
>> they want you to send information to Microsoft).
>> 5. I did not check the event log that is something I can review.
>> 6. Connection string:
>> m_strConnection = "data source=" + m_strSQLServerName + ";"
>> +
>> "initial catalog="+m_strDatabaseName+";integrated
>> security=SSPI;";
>> "William (Bill) Vaughn" <billvaRemoveThis@.nwlink.com> wrote in message
>> news:eZi8YW2LHHA.3668@.TK2MSFTNGP02.phx.gbl...
>> Let's hear a bit more about your configuration. I assume you're
>> expecting an existing SQL Express instance on the client system. Is it
>> running? How are the clients authenticated? I assume you have a
>> Try/Catch around the Open. Does the exception occur there? Is there a
>> number with the error message? Did you check the client systems event
>> log? Let's see the ConnectionString.
>> --
>> ____________________________________
>> William (Bill) Vaughn
>> Author, Mentor, Consultant
>> Microsoft MVP
>> INETA Speaker
>> www.betav.com/blog/billva
>> www.betav.com
>> Please reply only to the newsgroup so that others can benefit.
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> __________________________________
>> Visit www.hitchhikerguides.net to get more information on my latest
>> book:
>> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
>> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
>> ------
>> "Earl" <brikshoe@.newsgroups.nospam> wrote in message
>> news:uHqd6%230LHHA.2232@.TK2MSFTNGP02.phx.gbl...
>>I have an issue that is totally baffling me. When I use a program I've
>>written to connect to SQLExpress (and a given database), all works
>>well on my development system and on a laptop that I tested with.
>>However, I have two users that I sent the SAME database files and
>>program files to and at the moment the program tries to connect to the
>>server/database, they get the generic Windows error message "[Your
>>Program] has encountered an error and needs to close. We are sorry for
>>the inconvenience."
>> This differs from handled exceptions and unhandled exceptions within
>> the program. I have had the users uninstall their older SQLExpress
>> and update to the recent service pack, checked various configuration
>> settings, including owner of the database, including allowed remote
>> connections, both TCP/IP and NamedPipe. Everything "looks" correct,
>> but no connection and the above-mentioned Windows error message. I am
>> just stumped, so I'd love to hear any ideas or advice from anyone who
>> has seen this before.
>>
>>
>>
>>
>

Error when connecting to sql 2000

I am trying to connect to a sql 2k database using a Microsoft Application block. I get the following error. It is saying about 2005, I verified that SQL 2K is running on the server.

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

Any help will be appreciated.

Hi,

1. Verify the firewall have open the port of SQL 2K,

2. the Service pack versión I have some problems with versions under sp4

greetings.

|||

Hi jijo_robert,

That's a common issue. If you perform a search through google for the error message you are getting, you will find many valuable solutions.

The first thing for you to do is to check your connection string, make sure you have used the correct server name, database name , authentication mode,,.etc

If you still cannot figure it out, open up your query analyzer and connect to your database manually, see if you can login this way(there is a possibility that there maybe some problem in the server side)

Hope my suggestion helps

|||I could connect using sql query analyzer. I can also connect during design time (Gridview --> SQLDatasource --> and see the records with a connection string) but when I run it it gives this error.|||Make sure that you don't have any other program using the database other than Visual Web Developer if that is what u're using, or having the connection open. What mostly cause this kind of problem is when you have your database open in the database explorer of your VWD or VS.Hope this works.Please give me the appropriate make if this works for this is my first post on the forums|||

No other program is using SQL server databsae

Error when connecting to server via SQL 2005 Management Studio in Object Explorer but not Query

Hi,

I'm getting the error below when I attempt to connect to a remote Sql 2005 server using Management Studio and the Object Explorer. The same error does not occur if I go through "New > Database Engine Query" and fill out the same connection dialog with the exact same information. FYI, I am connecting to the IP of an external SQL 2005 server via SQL Server Authentication, and there is some level of connection going on as connecting with the wrong authentication information gives me a standard authentication error even while using the Object Explorer dialog. I am able to do all operations I need in the database engine query window without problem.

---

Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)

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

A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The specified network name is no longer available.) (Microsoft SQL Server, Error: 64)

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

---

Any ideas on why this would occur? I know this is a standard "network issue" type problem but I'm not aware of any difference that would allow the connection to work fine in one and not the other.

Thanks!

I have this exact error too. Please post if you have made progress on this.

-H

|||Same error here as well. I can connect using 2005 management studio from my XP workstation, but my Vista machine throws this error.|||OK - Same error - also from a Vista machine. Has anyone found the solution|||I think there is some problem with the object explorer dlls. I got the error after installing MDAC 2.7. When i connect it says some dll does registered, but i can connect thru database engine query.|||This shouldn't be related to MDAC at all. Management Studio doesn't use MDAC for any connections. How are you establishing your connections (using server name or IP)?|||

I suspect you are running into a firewall issue on Vista. The built-in firewall on Vista is much more capable than the XP firewall. The Vista firewall can block outbound connections as well as the inbound connections the XP firewall can block.

Make sure you add a firewall exception for sqlwb.exe (the management studio executable). You might need to open up port 1433 TCP as well.

Hope this helps,

Steve

Error when connecting to server via SQL 2005 Management Studio in Object Explorer but not Query

Hi,

I'm getting the error below when I attempt to connect to a remote Sql 2005 server using Management Studio and the Object Explorer. The same error does not occur if I go through "New > Database Engine Query" and fill out the same connection dialog with the exact same information. FYI, I am connecting to the IP of an external SQL 2005 server via SQL Server Authentication, and there is some level of connection going on as connecting with the wrong authentication information gives me a standard authentication error even while using the Object Explorer dialog. I am able to do all operations I need in the database engine query window without problem.

---

Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)

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

A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The specified network name is no longer available.) (Microsoft SQL Server, Error: 64)

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

---

Any ideas on why this would occur? I know this is a standard "network issue" type problem but I'm not aware of any difference that would allow the connection to work fine in one and not the other.

Thanks!

I have this exact error too. Please post if you have made progress on this.

-H

|||Same error here as well. I can connect using 2005 management studio from my XP workstation, but my Vista machine throws this error.|||OK - Same error - also from a Vista machine. Has anyone found the solution|||I think there is some problem with the object explorer dlls. I got the error after installing MDAC 2.7. When i connect it says some dll does registered, but i can connect thru database engine query.|||This shouldn't be related to MDAC at all. Management Studio doesn't use MDAC for any connections. How are you establishing your connections (using server name or IP)?|||

I suspect you are running into a firewall issue on Vista. The built-in firewall on Vista is much more capable than the XP firewall. The Vista firewall can block outbound connections as well as the inbound connections the XP firewall can block.

Make sure you add a firewall exception for sqlwb.exe (the management studio executable). You might need to open up port 1433 TCP as well.

Hope this helps,

Steve