When I run the rskeymgmt program to backup the encryption key, I get the
following error:
The Report Server Windows service is not responding to RPC requests. The
service may not be running.
I have checked, and the service is running. We are using SQL Server 2005
sp2. The command I am using is:
rskeymgmt -e -fc:\rskey\rsdbkey.txt -psomepassword
Any ideas why this is failing. I was able to run the program some time ago.
Thanks.On May 2, 11:50 am, "Tim Kelley" <tkel...@.company.com> wrote:
> When I run the rskeymgmt program to backup the encryption key, I get the
> following error:
> The Report Server Windows service is not responding to RPC requests. The
> service may not be running.
> I have checked, and the service is running. We are using SQL Server 2005
> sp2. The command I am using is:
> rskeymgmt -e -fc:\rskey\rsdbkey.txt -psomepassword
> Any ideas why this is failing. I was able to run the program some time ago.
> Thanks.
This link might be helpful:
http://www.technologyone.org/new-6210113-3731.html
Regards,
Enrique Martinez
Sr. Software Consultant
Showing posts with label program. Show all posts
Showing posts with label program. Show all posts
Thursday, March 29, 2012
Friday, March 23, 2012
Error when installing
i'm trying to install MS server 2000 components and I continuously get the same error. "A previous program installation created pending file operations on the installation machine. You must restart the computer before running setup." I've rebooted 100 times, turned the machine on and off, installed other programs, etc. and stil I get the error ONLY when I try to install the components.
Please Help!!!!
Thanks.
Moved to the setup group for a better chance of a response.|||try...
http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/q290/9/91.asp&NoWebContent=1
|||Hi, this should help:
http://support.microsoft.com/default.aspx?scid=kb;en-us;312995
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
sqlError when installing
i'm trying to install MS server 2000 components and I continuously get the same error. "A previous program installation created pending file operations on the installation machine. You must restart the computer before running setup." I've rebooted 100 times, turned the machine on and off, installed other programs, etc. and stil I get the error ONLY when I try to install the components.
Please Help!!!!
Thanks.
Moved to the setup group for a better chance of a response.|||try...
http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/q290/9/91.asp&NoWebContent=1
|||Hi, this should help:
http://support.microsoft.com/default.aspx?scid=kb;en-us;312995
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
Error when inserting datetime in german SQL Server 2000
Hello!
I have a program that are using a stored procedure to insert a row in
an SQL Server. During several years this program has worked fine using
an English version of SQL server. Now a customer wants to use a german
SQL server, but it doesn't work. The row is never inserted. I get the
following error:
[Microsoft][ODBC SQL Server Driver][SQL Server]Fehler beim
Konvertieren von Datentyp varchar in datetime.
Now, if I change the language setting to english in the "SQL Server
Login properties for 'sa'" it all works. If I restore the language
setting to german in the "SQL Server Login properties for 'sa'", it
all continues to work until I re-boot the PC. When I have re-booted, I
once gain end up with the error that I have described before.
It seems strange to me that SQL Server doesn't behave in a consistent
way. Sometimes it works with german language settings, sometimes it
doesn't.
Any explanations would be very appriciated.
BR / PatrikThis is because dateformat changes according to language settings.
date format considerations while insert and update:
You can SET DATEFORMAT and modify code as follows.
create table test(dt datetime)
go
declare @.dt varchar(32)
set @.dt ='26/07/2002'
set dateformat dmy --change dateformat
insert into test values(convert(datetime,@.dt)) ;
select * from test;
go
OR other method would be to use explicit coversion of the
date using CONVERT function.
create table test(dt datetime)
go
declare @.dt varchar(32)
set @.dt ='26/07/2002'
insert into test values(convert(datetime,@.dt, 103)) ;
select * from test;
go
--
-Vishal
"Patrik Johansson" <patrikmjohansson@.yahoo.se> wrote in message
news:8d5c526d.0307010514.b59427d@.posting.google.com...
> Hello!
> I have a program that are using a stored procedure to insert a row in
> an SQL Server. During several years this program has worked fine using
> an English version of SQL server. Now a customer wants to use a german
> SQL server, but it doesn't work. The row is never inserted. I get the
> following error:
> [Microsoft][ODBC SQL Server Driver][SQL Server]Fehler beim
> Konvertieren von Datentyp varchar in datetime.
> Now, if I change the language setting to english in the "SQL Server
> Login properties for 'sa'" it all works. If I restore the language
> setting to german in the "SQL Server Login properties for 'sa'", it
> all continues to work until I re-boot the PC. When I have re-booted, I
> once gain end up with the error that I have described before.
> It seems strange to me that SQL Server doesn't behave in a consistent
> way. Sometimes it works with german language settings, sometimes it
> doesn't.
> Any explanations would be very appriciated.
> BR / Patrik|||Patrik,
Yes, language and localizations are a problem to deal with. You might find
this topic helpful:
Writing International Transact-SQL Statements in the MSDN at:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/acdata/ac_8_qd_14_3unn.asp
You can also manage this by setting the language of the connection that is
transmitting data. For this use: SET LANGUAGE xxx for a connection or use
sp_defaultlanguage to set the default for a login.
Russell Fields
"Patrik Johansson" <patrikmjohansson@.yahoo.se> wrote in message
news:8d5c526d.0307010514.b59427d@.posting.google.com...
> Hello!
> I have a program that are using a stored procedure to insert a row in
> an SQL Server. During several years this program has worked fine using
> an English version of SQL server. Now a customer wants to use a german
> SQL server, but it doesn't work. The row is never inserted. I get the
> following error:
> [Microsoft][ODBC SQL Server Driver][SQL Server]Fehler beim
> Konvertieren von Datentyp varchar in datetime.
> Now, if I change the language setting to english in the "SQL Server
> Login properties for 'sa'" it all works. If I restore the language
> setting to german in the "SQL Server Login properties for 'sa'", it
> all continues to work until I re-boot the PC. When I have re-booted, I
> once gain end up with the error that I have described before.
> It seems strange to me that SQL Server doesn't behave in a consistent
> way. Sometimes it works with german language settings, sometimes it
> doesn't.
> Any explanations would be very appriciated.
> BR / Patrik|||Pass the date in YYYYMMDD or YYYY-MM-DD format. Then there is no confusion
for people *or* the software.
"Patrik Johansson" <patrikmjohansson@.yahoo.se> wrote in message
news:8d5c526d.0307010514.b59427d@.posting.google.com...
> Hello!
> I have a program that are using a stored procedure to insert a row in
> an SQL Server. During several years this program has worked fine using
> an English version of SQL server. Now a customer wants to use a german
> SQL server, but it doesn't work. The row is never inserted. I get the
> following error:
> [Microsoft][ODBC SQL Server Driver][SQL Server]Fehler beim
> Konvertieren von Datentyp varchar in datetime.
> Now, if I change the language setting to english in the "SQL Server
> Login properties for 'sa'" it all works. If I restore the language
> setting to german in the "SQL Server Login properties for 'sa'", it
> all continues to work until I re-boot the PC. When I have re-booted, I
> once gain end up with the error that I have described before.
> It seems strange to me that SQL Server doesn't behave in a consistent
> way. Sometimes it works with german language settings, sometimes it
> doesn't.
> Any explanations would be very appriciated.
> BR / Patrik|||Only YYYYMMDD without any separators works always:
SET DATEFORMAT dmy
SELECT ISDATE('2003-07-13'), ISDATE('20030713')
SET DATEFORMAT mdy
SELECT ISDATE('2003-07-13'), ISDATE('20030713')
I can see that you as an American are not that used to dealing with date
formats as I as a European am ;-)
Jacco Schalkwijk MCDBA, MCSD, MCSE
Database Administrator
Eurostop Ltd.
"Aaron Bertrand - MVP" <aaron@.TRASHaspfaq.com> wrote in message
news:uame7U9PDHA.2768@.tk2msftngp13.phx.gbl...
> Pass the date in YYYYMMDD or YYYY-MM-DD format. Then there is no
confusion
> for people *or* the software.
>
> "Patrik Johansson" <patrikmjohansson@.yahoo.se> wrote in message
> news:8d5c526d.0307010514.b59427d@.posting.google.com...
> > Hello!
> >
> > I have a program that are using a stored procedure to insert a row in
> > an SQL Server. During several years this program has worked fine using
> > an English version of SQL server. Now a customer wants to use a german
> > SQL server, but it doesn't work. The row is never inserted. I get the
> > following error:
> >
> > [Microsoft][ODBC SQL Server Driver][SQL Server]Fehler beim
> > Konvertieren von Datentyp varchar in datetime.
> >
> > Now, if I change the language setting to english in the "SQL Server
> > Login properties for 'sa'" it all works. If I restore the language
> > setting to german in the "SQL Server Login properties for 'sa'", it
> > all continues to work until I re-boot the PC. When I have re-booted, I
> > once gain end up with the error that I have described before.
> >
> > It seems strange to me that SQL Server doesn't behave in a consistent
> > way. Sometimes it works with german language settings, sometimes it
> > doesn't.
> >
> > Any explanations would be very appriciated.
> >
> > BR / Patrik
>|||> I can see that you as an American are not that used to dealing with date
> formats as I as a European am ;-)
Hey, don't call me an American... I'm a Canuck, just ask Tom...
:-Psql
I have a program that are using a stored procedure to insert a row in
an SQL Server. During several years this program has worked fine using
an English version of SQL server. Now a customer wants to use a german
SQL server, but it doesn't work. The row is never inserted. I get the
following error:
[Microsoft][ODBC SQL Server Driver][SQL Server]Fehler beim
Konvertieren von Datentyp varchar in datetime.
Now, if I change the language setting to english in the "SQL Server
Login properties for 'sa'" it all works. If I restore the language
setting to german in the "SQL Server Login properties for 'sa'", it
all continues to work until I re-boot the PC. When I have re-booted, I
once gain end up with the error that I have described before.
It seems strange to me that SQL Server doesn't behave in a consistent
way. Sometimes it works with german language settings, sometimes it
doesn't.
Any explanations would be very appriciated.
BR / PatrikThis is because dateformat changes according to language settings.
date format considerations while insert and update:
You can SET DATEFORMAT and modify code as follows.
create table test(dt datetime)
go
declare @.dt varchar(32)
set @.dt ='26/07/2002'
set dateformat dmy --change dateformat
insert into test values(convert(datetime,@.dt)) ;
select * from test;
go
OR other method would be to use explicit coversion of the
date using CONVERT function.
create table test(dt datetime)
go
declare @.dt varchar(32)
set @.dt ='26/07/2002'
insert into test values(convert(datetime,@.dt, 103)) ;
select * from test;
go
--
-Vishal
"Patrik Johansson" <patrikmjohansson@.yahoo.se> wrote in message
news:8d5c526d.0307010514.b59427d@.posting.google.com...
> Hello!
> I have a program that are using a stored procedure to insert a row in
> an SQL Server. During several years this program has worked fine using
> an English version of SQL server. Now a customer wants to use a german
> SQL server, but it doesn't work. The row is never inserted. I get the
> following error:
> [Microsoft][ODBC SQL Server Driver][SQL Server]Fehler beim
> Konvertieren von Datentyp varchar in datetime.
> Now, if I change the language setting to english in the "SQL Server
> Login properties for 'sa'" it all works. If I restore the language
> setting to german in the "SQL Server Login properties for 'sa'", it
> all continues to work until I re-boot the PC. When I have re-booted, I
> once gain end up with the error that I have described before.
> It seems strange to me that SQL Server doesn't behave in a consistent
> way. Sometimes it works with german language settings, sometimes it
> doesn't.
> Any explanations would be very appriciated.
> BR / Patrik|||Patrik,
Yes, language and localizations are a problem to deal with. You might find
this topic helpful:
Writing International Transact-SQL Statements in the MSDN at:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/acdata/ac_8_qd_14_3unn.asp
You can also manage this by setting the language of the connection that is
transmitting data. For this use: SET LANGUAGE xxx for a connection or use
sp_defaultlanguage to set the default for a login.
Russell Fields
"Patrik Johansson" <patrikmjohansson@.yahoo.se> wrote in message
news:8d5c526d.0307010514.b59427d@.posting.google.com...
> Hello!
> I have a program that are using a stored procedure to insert a row in
> an SQL Server. During several years this program has worked fine using
> an English version of SQL server. Now a customer wants to use a german
> SQL server, but it doesn't work. The row is never inserted. I get the
> following error:
> [Microsoft][ODBC SQL Server Driver][SQL Server]Fehler beim
> Konvertieren von Datentyp varchar in datetime.
> Now, if I change the language setting to english in the "SQL Server
> Login properties for 'sa'" it all works. If I restore the language
> setting to german in the "SQL Server Login properties for 'sa'", it
> all continues to work until I re-boot the PC. When I have re-booted, I
> once gain end up with the error that I have described before.
> It seems strange to me that SQL Server doesn't behave in a consistent
> way. Sometimes it works with german language settings, sometimes it
> doesn't.
> Any explanations would be very appriciated.
> BR / Patrik|||Pass the date in YYYYMMDD or YYYY-MM-DD format. Then there is no confusion
for people *or* the software.
"Patrik Johansson" <patrikmjohansson@.yahoo.se> wrote in message
news:8d5c526d.0307010514.b59427d@.posting.google.com...
> Hello!
> I have a program that are using a stored procedure to insert a row in
> an SQL Server. During several years this program has worked fine using
> an English version of SQL server. Now a customer wants to use a german
> SQL server, but it doesn't work. The row is never inserted. I get the
> following error:
> [Microsoft][ODBC SQL Server Driver][SQL Server]Fehler beim
> Konvertieren von Datentyp varchar in datetime.
> Now, if I change the language setting to english in the "SQL Server
> Login properties for 'sa'" it all works. If I restore the language
> setting to german in the "SQL Server Login properties for 'sa'", it
> all continues to work until I re-boot the PC. When I have re-booted, I
> once gain end up with the error that I have described before.
> It seems strange to me that SQL Server doesn't behave in a consistent
> way. Sometimes it works with german language settings, sometimes it
> doesn't.
> Any explanations would be very appriciated.
> BR / Patrik|||Only YYYYMMDD without any separators works always:
SET DATEFORMAT dmy
SELECT ISDATE('2003-07-13'), ISDATE('20030713')
SET DATEFORMAT mdy
SELECT ISDATE('2003-07-13'), ISDATE('20030713')
I can see that you as an American are not that used to dealing with date
formats as I as a European am ;-)
Jacco Schalkwijk MCDBA, MCSD, MCSE
Database Administrator
Eurostop Ltd.
"Aaron Bertrand - MVP" <aaron@.TRASHaspfaq.com> wrote in message
news:uame7U9PDHA.2768@.tk2msftngp13.phx.gbl...
> Pass the date in YYYYMMDD or YYYY-MM-DD format. Then there is no
confusion
> for people *or* the software.
>
> "Patrik Johansson" <patrikmjohansson@.yahoo.se> wrote in message
> news:8d5c526d.0307010514.b59427d@.posting.google.com...
> > Hello!
> >
> > I have a program that are using a stored procedure to insert a row in
> > an SQL Server. During several years this program has worked fine using
> > an English version of SQL server. Now a customer wants to use a german
> > SQL server, but it doesn't work. The row is never inserted. I get the
> > following error:
> >
> > [Microsoft][ODBC SQL Server Driver][SQL Server]Fehler beim
> > Konvertieren von Datentyp varchar in datetime.
> >
> > Now, if I change the language setting to english in the "SQL Server
> > Login properties for 'sa'" it all works. If I restore the language
> > setting to german in the "SQL Server Login properties for 'sa'", it
> > all continues to work until I re-boot the PC. When I have re-booted, I
> > once gain end up with the error that I have described before.
> >
> > It seems strange to me that SQL Server doesn't behave in a consistent
> > way. Sometimes it works with german language settings, sometimes it
> > doesn't.
> >
> > Any explanations would be very appriciated.
> >
> > BR / Patrik
>|||> I can see that you as an American are not that used to dealing with date
> formats as I as a European am ;-)
Hey, don't call me an American... I'm a Canuck, just ask Tom...
:-Psql
Monday, March 19, 2012
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...
>
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...
>
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...
>
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.
>>
>>
>>
>>
>
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.
>>
>>
>>
>>
>
Wednesday, March 7, 2012
Error using Verify/Repair methods of SqlCeEngine
I have a compact pc program that uses a sql server database (sdf file).
I want to check the database integrity when program starts so I added a call to veriy method of SqlCeEngine.
The verify function always returns false even the database is OK and I can work with it.
when I call repair it throws the exception : "The specified module could not be found"
The code is :
string connectionString = "Data Source = '" + m_dbFullName + "'";
SqlCeEngine engine = new SqlCeEngine(connectionString);
if(engine.Verify() == false)
{
engine.Repair(null, RepairOption.RecoverCorruptedRows);
}
The database exists and the path to it is correct:
dbFullName = "\\program files\\MyApp\\MyDB.sdf"
I also tried out some different connection strings but it did not help:
"Data Source = ' MyDB.sdf '"
"Data Source = 'MyDB.sdf "
"Data Source=' MyDB.sdf '"
"Data Source=MyDB.sdf"
Please any one can help me with this ?
I have the same problem...Wednesday, February 15, 2012
Error S1003 ... Program Type Out Of Range
I am receiving an "S1003 ... Program Type Out Of Range" error when retrievin
g data but cannot find any additional documented help on it's meaning nor a
solution to the problem.
Any and all help is greatly appreciated.
Thanks,
Jim.This doesn't look like a SQL Server error. I suggest you ask the vendor of t
he application what this
means.
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=...ls
erver
"JimJNH" <anonymous@.discussions.microsoft.com> wrote in message
news:722C411A-6C52-439B-87C8-8F697A2BA05B@.microsoft.com...
any additional documented help on it's meaning nor a solution to the problem.
Select Error: SQLSTATE = S1003
[Microsoft][ODBC Driver Manager] Program Type Out of range
The Select works fine with other ODBC drivers (Sybase, Oracle, ...) but fail
s with SQL Server.
-- Tibor Karaszi wrote: --
This doesn't look like a SQL Server error. I suggest you ask the vendor of t
he application what this
means.
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=...ls
erver
"JimJNH" <anonymous@.discussions.microsoft.com> wrote in message
news:722C411A-6C52-439B-87C8-8F697A2BA05B@.microsoft.com...
any additional documented help on it's meaning nor a solution to the problem.[QUOTE][color=darkred
]
g data but cannot find any additional documented help on it's meaning nor a
solution to the problem.
Any and all help is greatly appreciated.
Thanks,
Jim.This doesn't look like a SQL Server error. I suggest you ask the vendor of t
he application what this
means.
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=...ls
erver
"JimJNH" <anonymous@.discussions.microsoft.com> wrote in message
news:722C411A-6C52-439B-87C8-8F697A2BA05B@.microsoft.com...
quote:
> I am receiving an "S1003 ... Program Type Out Of Range" error when retrieving data but can
not find
any additional documented help on it's meaning nor a solution to the problem.
quote:|||The ODBC Error comes up exactly as follows:
> Any and all help is greatly appreciated.
> Thanks,
> Jim.
Select Error: SQLSTATE = S1003
[Microsoft][ODBC Driver Manager] Program Type Out of range
The Select works fine with other ODBC drivers (Sybase, Oracle, ...) but fail
s with SQL Server.
-- Tibor Karaszi wrote: --
This doesn't look like a SQL Server error. I suggest you ask the vendor of t
he application what this
means.
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=...ls
erver
"JimJNH" <anonymous@.discussions.microsoft.com> wrote in message
news:722C411A-6C52-439B-87C8-8F697A2BA05B@.microsoft.com...
quote:
> I am receiving an "S1003 ... Program Type Out Of Range" error when retrieving data but can
not find
any additional documented help on it's meaning nor a solution to the problem.[QUOTE][color=darkred
]
Error S1003 ... Program Type Out Of Range
I am receiving an "S1003 ... Program Type Out Of Range" error when retrieving data but cannot find any additional documented help on it's meaning nor a solution to the problem.
Any and all help is greatly appreciated.
Thanks,
Jim.This doesn't look like a SQL Server error. I suggest you ask the vendor of the application what this
means.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"JimJNH" <anonymous@.discussions.microsoft.com> wrote in message
news:722C411A-6C52-439B-87C8-8F697A2BA05B@.microsoft.com...
> I am receiving an "S1003 ... Program Type Out Of Range" error when retrieving data but cannot find
any additional documented help on it's meaning nor a solution to the problem.
> Any and all help is greatly appreciated.
> Thanks,
> Jim.|||The ODBC Error comes up exactly as follows:
Select Error: SQLSTATE = S1003
[Microsoft][ODBC Driver Manager] Program Type Out of range
The Select works fine with other ODBC drivers (Sybase, Oracle, ...) but fails with SQL Server.
-- Tibor Karaszi wrote: --
This doesn't look like a SQL Server error. I suggest you ask the vendor of the application what this
means.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"JimJNH" <anonymous@.discussions.microsoft.com> wrote in message
news:722C411A-6C52-439B-87C8-8F697A2BA05B@.microsoft.com...
> I am receiving an "S1003 ... Program Type Out Of Range" error when retrieving data but cannot find
any additional documented help on it's meaning nor a solution to the problem.
>> Any and all help is greatly appreciated.
>> Thanks,
>> Jim.
Any and all help is greatly appreciated.
Thanks,
Jim.This doesn't look like a SQL Server error. I suggest you ask the vendor of the application what this
means.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"JimJNH" <anonymous@.discussions.microsoft.com> wrote in message
news:722C411A-6C52-439B-87C8-8F697A2BA05B@.microsoft.com...
> I am receiving an "S1003 ... Program Type Out Of Range" error when retrieving data but cannot find
any additional documented help on it's meaning nor a solution to the problem.
> Any and all help is greatly appreciated.
> Thanks,
> Jim.|||The ODBC Error comes up exactly as follows:
Select Error: SQLSTATE = S1003
[Microsoft][ODBC Driver Manager] Program Type Out of range
The Select works fine with other ODBC drivers (Sybase, Oracle, ...) but fails with SQL Server.
-- Tibor Karaszi wrote: --
This doesn't look like a SQL Server error. I suggest you ask the vendor of the application what this
means.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"JimJNH" <anonymous@.discussions.microsoft.com> wrote in message
news:722C411A-6C52-439B-87C8-8F697A2BA05B@.microsoft.com...
> I am receiving an "S1003 ... Program Type Out Of Range" error when retrieving data but cannot find
any additional documented help on it's meaning nor a solution to the problem.
>> Any and all help is greatly appreciated.
>> Thanks,
>> Jim.
Subscribe to:
Posts (Atom)