Error running report: connecting

Showing posts with label connecting. Show all posts

Thursday, March 29, 2012

Error when using SSL encryption for SQL server 2000

Hi,
I am having trouble connecting to SQL server 2000 using SSL.
My environment is as follows:
1. Microsoft Certificate server running on a Windows 2000 server machine.
2. SQL Server 2000 running on a Win NT machine with SP6 installed. SQL
Server service pack 3a has been installed.
3. Client machine running Windows XP with SQL Server service pack 3a
installed.
We use a type 4 JDBC secure driver to connect to SQL server from our Java ap
plication running on the client machine.
We also setup the certificate as described in the article 276553 - HOW TO: E
nable SSL Encryption for SQL Server 2000 with Certificate Server.
The installation of the certificate was successful. However, when I tried to
connect to the SQL server using SQL Query Analyzer, I received the followin
g error message.
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Encryption not supported on SQL Serv
er
Thanks,
Chacko.Usually, you receive that error if you enable SSL from the client and the
server doesn't have the certificate.
But, the bad news is you won't be able to use SSL with a type 4 Java driver.
The implementation of protocol encryption requires the driver to access
SSL. In
particular protocol encryption uses SSL APIs implemented in NT. Type 4 JDBC
drivers have a problem in that they are not allowed to directly call system
dlls. There is no library in Java 1.4 or below that emulates the protocol
encryption behavior of SSL from Windows NT.
If your JDBC application requires protocol encryption to SQL 2000,
you will have to use alternate method of encryption such as IPSEC or use a
suitable SSL enabled Type 3 JDBC Driver.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Hi Kevin,
Thanks for your response.
We did generate and install the certificate using the web browser and not us
ing MMC since it is a Win NT 4.0 box. When we look at the certificate on the
database server machine via the IE properties applet, the certificate shows
up fine as described in th
e Microsoft setup document. So, I am not sure where I am going wrong. Is the
re any way to trouble shoot this issue?
Also, we are not even trying the connectivity with the type 4 JDBC driver ye
t even though that is what we want to do ultimately. However, right now we a
re using Query Analyzer on the client machine to test the communication. We
get the error when we try a
nd login to the database via Query Analyzer.
About the type 4 JDBC driver, the documentation from i-net OPTA type 4 JDBC driver says
that it supports SSL for SQL Server 2000. Am I misunderstanding something here? You ca
n find information about i-net OPTA at [url]http://www.inetsoftware.de/English/Produkt[
/url]
e/OPTA/default.htm
Your thoughts are greatly appreciated.
Thanks Kevin.
Chacko.

Wednesday, March 21, 2012

Error when exporting to PDF

I am having an issue exporting reports to PDF.

I am connecting to the report server via https and all of the reports I'm using are working fine, but when I try and export the reports to PDF I run into problems.

On one machine running XP when I try and export a report to PDF; it will let me open the PDF, but if I try and 'save' the PDF it gives me an error that the site cannot be found.

On another machine running Windows 2000, I cannot save or open the report when trying to export to PDF with the same site cannot be found popup from Internet Explorer.

Anyone know of anything special that I need to setup to get this working? Could this be a mime type issue on the server?

Any help is greatly appreciated!

Just to add to this..

I am able to export to PDF and open on a machine running Acrobat reader 5.0,and a machine running Acrobat reader 6.0 but not from any computer running Acrobat reader 7.0!

Any ideas?

Monday, March 19, 2012

error when connecting trhough enterprise manager

hi all ,
i've got an application with sql databse. it runs correctly on the server.
when i go to windows Xp and installed the appliaction and run the sql
enterprise manager to connect to the server, i get the following error:
message =: ExecuteReader requires an open and available connection. the
connection's current state is closed.
i've checked network connection ..it is ok.
the same application we've tested at office ...its working fine.
plz advise
kryshzt
Hi
Are you sure? This error's message is pretty clear, isn't it?
"kryshzt" <kryshzt@.discussions.microsoft.com> wrote in message
news:8636B1D3-80F7-40C7-A384-3DC1E6E9C8ED@.microsoft.com...
> hi all ,
> i've got an application with sql databse. it runs correctly on the server.
> when i go to windows Xp and installed the appliaction and run the sql
> enterprise manager to connect to the server, i get the following error:
> message =: ExecuteReader requires an open and available connection. the
> connection's current state is closed.
> i've checked network connection ..it is ok.
> the same application we've tested at office ...its working fine.
> plz advise
> kryshzt

error when connecting trhough enterprise manager

hi all ,
i've got an application with sql databse. it runs correctly on the server.
when i go to Windows XP and installed the appliaction and run the sql
enterprise manager to connect to the server, i get the following error:
message =: ExecuteReader requires an open and available connection. the
connection's current state is closed.
i've checked network connection ..it is ok.
the same application we've tested at office ...its working fine.
plz advise
kryshztHi
Are you sure? This error's message is pretty clear, isn't it?
"kryshzt" <kryshzt@.discussions.microsoft.com> wrote in message
news:8636B1D3-80F7-40C7-A384-3DC1E6E9C8ED@.microsoft.com...
> hi all ,
> i've got an application with sql databse. it runs correctly on the server.
> when i go to Windows XP and installed the appliaction and run the sql
> enterprise manager to connect to the server, i get the following error:
> message =: ExecuteReader requires an open and available connection. the
> connection's current state is closed.
> i've checked network connection ..it is ok.
> the same application we've tested at office ...its working fine.
> plz advise
> kryshzt

error when connecting trhough enterprise manager

hi all ,
i've got an application with sql databse. it runs correctly on the server.
when i go to windows Xp and installed the appliaction and run the sql
enterprise manager to connect to the server, i get the following error:
message =: ExecuteReader requires an open and available connection. the
connection's current state is closed.
i've checked network connection ..it is ok.
the same application we've tested at office ...its working fine.
plz advise
kryshztHi
Are you sure? This error's message is pretty clear, isn't it?
"kryshzt" <kryshzt@.discussions.microsoft.com> wrote in message
news:8636B1D3-80F7-40C7-A384-3DC1E6E9C8ED@.microsoft.com...
> hi all ,
> i've got an application with sql databse. it runs correctly on the server.
> when i go to windows Xp and installed the appliaction and run the sql
> enterprise manager to connect to the server, i get the following error:
> message =: ExecuteReader requires an open and available connection. the
> connection's current state is closed.
> i've checked network connection ..it is ok.
> the same application we've tested at office ...its working fine.
> plz advise
> kryshzt

Error when connecting to SSIS.

I just installed a default instance of SS 2005 and applied the most recent service pack, release date March 5th, SQLServer2005SP2-KB921896-x64-ENU.exe.

All services are running as localsystem. When I try to connect to SSIS through Management Studio on the local machine I receive the following error.

Any help would be appreciated.

TITLE: Connect to Server

Cannot connect to [server name].

ADDITIONAL INFORMATION:
Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476

Connect to SSIS Service on machine "[server name]" failed:
Error loading type library/DLL.
.

Connect to SSIS Service on machine "[server name]." failed:
Error loading type library/DLL.
.

BUTTONS:
OK

Do you have the SQL Server SSIS service started (running)?|||I do.|||

There was one thing that was a little weird. I tried re-installing the Service Pack and it did not recognize that the services were running or would interfere with the install.

The first time I installed SP2 it forced me to stop the services before installing, but the second time it did not. Seemed as if the install did not detect the services were running.

After installing the second time, I did a reboot to attempt to clear it up. SSIS still did not allow a connection and I received the same error.

|||Does this help? Are you also running SQL Server 2000?

http://sqljunkies.com/WebLog/knight_reign/archive/2005/06/08/15765.aspx|||No not running SQL 2000 on this computer. It is a brand new server.|||

I am looking at the link you sent, thought this may be relevant also.

There was a previous named instance that I uninstalled, before installing the default instance. There were no other instances on the computer after I uninstalled the named instance.

|||

Phil,

The xml ini file in the link appears to be correct on my server.

It shows the servername as <ServerName>.</ServerName>.

I appreciate the help, so does my client. ;)

|||

Phil,

The issue on the post at this site seems to be the same.

http://www.kbalertz.com/Feedback_926629.aspx

The cause is listed as "This problem occurs because the 32-bit Dts.dll file is unregistered when the 64-bit SSIS is installed as part of the hotfix.". Does this ring a bell?

|||Have you tried reinstalling the client tools?|||

SnoChoJoe wrote:
Phil,
The issue on the post at this site seems to be the same.
http://www.kbalertz.com/Feedback_926629.aspx
The cause is listed as "This problem occurs because the 32-bit Dts.dll file is unregistered when the 64-bit SSIS is installed as part of the hotfix.". Does this ring a bell?

I just read that myself. Are you on a 32 bit machine? The SP2 service pack you indicated is for 64 bit.|||No it is an X64 architecture.|||No I have not, you know I get an error on the Client Tools Update when installing SP2. Could that be related?|||

SnoChoJoe wrote:
No I have not, you know I get an error on the Client Tools Update when installing SP2. Could that be related?

Perhaps... Make sure you have a working installation before applying any service packs.|||

Ok, I am going to trouble shoot the client install.

I will advise if I determine the problem. Thanks Phil.

Error when connecting to SSIS.

I just installed a default instance of SS 2005 and applied the most recent service pack, release date March 5th, SQLServer2005SP2-KB921896-x64-ENU.exe.

All services are running as localsystem. When I try to connect to SSIS through Management Studio on the local machine I receive the following error.

Any help would be appreciated.

TITLE: Connect to Server

Cannot connect to [server name].

ADDITIONAL INFORMATION:
Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476

Connect to SSIS Service on machine "[server name]" failed:
Error loading type library/DLL.
.

Connect to SSIS Service on machine "[server name]." failed:
Error loading type library/DLL.
.

BUTTONS:
OK

Do you have the SQL Server SSIS service started (running)?|||I do.|||

There was one thing that was a little weird. I tried re-installing the Service Pack and it did not recognize that the services were running or would interfere with the install.

The first time I installed SP2 it forced me to stop the services before installing, but the second time it did not. Seemed as if the install did not detect the services were running.

After installing the second time, I did a reboot to attempt to clear it up. SSIS still did not allow a connection and I received the same error.

|||Does this help? Are you also running SQL Server 2000?

http://sqljunkies.com/WebLog/knight_reign/archive/2005/06/08/15765.aspx|||No not running SQL 2000 on this computer. It is a brand new server.|||

I am looking at the link you sent, thought this may be relevant also.

There was a previous named instance that I uninstalled, before installing the default instance. There were no other instances on the computer after I uninstalled the named instance.

|||

Phil,

The xml ini file in the link appears to be correct on my server.

It shows the servername as <ServerName>.</ServerName>.

I appreciate the help, so does my client. ;)

|||

Phil,

The issue on the post at this site seems to be the same.

http://www.kbalertz.com/Feedback_926629.aspx

The cause is listed as "This problem occurs because the 32-bit Dts.dll file is unregistered when the 64-bit SSIS is installed as part of the hotfix.". Does this ring a bell?

|||Have you tried reinstalling the client tools?|||

SnoChoJoe wrote:
Phil,
The issue on the post at this site seems to be the same.
http://www.kbalertz.com/Feedback_926629.aspx
The cause is listed as "This problem occurs because the 32-bit Dts.dll file is unregistered when the 64-bit SSIS is installed as part of the hotfix.". Does this ring a bell?

SnoChoJoe wrote:
No I have not, you know I get an error on the Client Tools Update when installing SP2. Could that be related?

Perhaps... Make sure you have a working installation before applying any service packs.|||

Ok, I am going to trouble shoot the client install.

I will advise if I determine the problem. Thanks Phil.

Error when connecting to SQLExpress

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

Error when connecting to SQL Server

when i tried connecting to SQL Server Express I got this error, be it connecting via Windows Authentication or SQL Authentication. Pls see below for the error message:

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

Cannot connect to JOHNSON\SQLEXPRESS.

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

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

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

Error Number: -1
Severity: 20
State: 0

Program Location:

at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Connect(Boolean& useFailoverPartner, Boolean& failoverDemandDone, String host, String failoverPartner, String protocol, SqlInternalConnectionTds connHandler, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject, Boolean aliasLookup)
at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup)
at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.ValidateConnection(UIConnectionInfo ci, IServerType server)
at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()

wats wrong with my setup? Previously it can connect. till i upgraded to SQL Server 2005 then uninstall my SQL Server 2005 then it become like tt....

what shld i do?

Pls advise.

Thanks

Johnson

Did you enable remote connections ? This is disabled by default. See the Screencast on my site for more information.

Jens K. Suessmeyer.

http://www.sqlserver2005.de
|||

Hi,

THanks for the reply but when i look into ur screencast and followed the steps to enable remote connection, I got the below error when try to click on the Surface Area Configureation.

"===================================

No SQL Server 2005 components were found on the specified computer. Either no components are installed, or you are not an administrator on this computer. (SQLSAC)

Program Location:

at Microsoft.SqlSac.MainPanel.FormServicesAndProtocols.ProcessClassConstructor()"

By the way y do i nd to enable remote connection when i am trying to connect to only my local SQLExpress?

I am using SQL Express and not SQL Server 2005.

Thanks

Johnson

|||Are you trying to configure the local computer ?|||

ya i m trying to access my SQL Mobile database using my SQL Server Management Studio Express. But when i tried connecting using SQL Server Management Studio Express to my local machine, I got thrown the error.

As mentioned I previously upgraded my SQL Server Express to SQL Server 2005. Thereafter I uninstall my SQL Server 2005 and reinstall ym VS 2005. So i duno is it cos of this. If so, wat shld I do to resolve this?

Can u advise wat's wrong?

Thanks

Johnson

|||

Hi Johnson,

I'm trying to understand what you're really trying to do here because your information is conflicting, maybe you can clarify a bit...

Are you trying to work with SQL Mobile or SQL Express? They are two different products. Do you have SQL Express installed or not? You've claimed that you installed it, then uninstalled it. You can't connect to it if you've uninstalled it. Do you have an entry on your Start menu for Microsoft SQL Server 2005? What is on it?|||

SQL Network Interfaces, error: 26 - Error Locating Server/Instance SpecifiedSQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified

This usually means the application cannot contact your SQL Browser. So, make sure SQL Browser is running and it's firewalled(put sqlbrowser.exe or UDP 1434 into exception).

|||

Hi Thanks..

I resolve the problem already. cos there isnt any SQL Server instance installed

Thanks

Johnson

Error when connecting to SQL Express

Hi - can anyone please help?

I am using SQL Express 2005 - and have an asp (yes legacy asp) site running locally. It works ok, until I try and connect to the server from another PC.

The error message I get is:

******

Microsoft OLE DB Provider for SQL Servererror '80004005'

Cannot open database "fixit" requested by the login. The login failed.

/fixitnew/fixit_login.asp, line 30

******

Line 30, is where I open the connection to the database.

My connection string is:

myConn = "Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=fixit;Data Source=misinvaknb01\sqlexpress;"

Can anyone please help?

Thanks in advance,

Mark

Default user has no permission to access fixit database . Follow those steps:

In Management Studio choose Security->Logins ->WindowsUserName->right click choose property->UserMapping -->Checkfixit database

Hope it helps.

Error when connecting to sql 2000

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

System.Data.SqlClient.SqlException: An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings

Any help will be appreciated.

Hi,

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

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

greetings.

|||

Hi jijo_robert,

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

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

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

Hope my suggestion helps

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

No other program is using SQL server databsae

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

Hi,

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

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

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

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

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

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

Thanks!

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

-H

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

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

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

Hope this helps,

Steve

Thursday, March 29, 2012

Error when using SSL encryption for SQL server 2000

Wednesday, March 21, 2012

Error when exporting to PDF

Monday, March 19, 2012

error when connecting trhough enterprise manager

error when connecting trhough enterprise manager

error when connecting trhough enterprise manager

Error when connecting to SSIS.

Error when connecting to SSIS.

Error when connecting to SQLExpress

Error when connecting to SQLExpress

Error when connecting to SQLExpress

Error when connecting to SQLExpress

Error when connecting to SQL Server

Error when connecting to SQL Express

Error when connecting to sql 2000

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

Error running report

Blog Archive

About Me