SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


SQL-08S01


SQL-08S01

Author
Message
Erico Galdino Almeida
Erico Galdino Almeida
Old Hand
Old Hand (306 reputation)Old Hand (306 reputation)Old Hand (306 reputation)Old Hand (306 reputation)Old Hand (306 reputation)Old Hand (306 reputation)Old Hand (306 reputation)Old Hand (306 reputation)

Group: General Forum Members
Points: 306 Visits: 1

Hello All

I'm facing a problem with an application, but I couldn't solve it even with the posts that I found here.

Enviromemnt:
I have one server with an LMS (Blackboard - Win2003 - SQL Server 2000 Client Tools - JAVA) and a Database server (Win2003 - SQL SERVER).
Application and Database are running in different networks.

Problem:
When I access the home page of the application, sometimes it appears an error message: "Database Error" Then, if I just reload the page, one or two times, it works properly, with no error message at all. After one hour or so, the same error occurs again.

In the log messages of the application I have the following:
*** 'E:\blackboard\bin\entry_rightpanel.pl' log message at: 2005/02/01 17:08:00
[Tue Feb 1 17:08:00 2005]: can't execute:
SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED SELECT pk1,sos_id_pk2,bgcolor,vlink,link,short_name,page_title,name,vhost,homepage,style,
course_image_main_src,course_image_main_link,course_image_main_name,
course_image_2_src,course_image_2_link,course_image_2_name,
course_image_nav_src,course_image_nav_link,course_image_nav_name,courses_row_height,
org_image_main_src,org_image_main_link,org_image_main_name,org_image_2_src,
org_image_2_link,org_image_2_name,org_image_nav_src,org_image_nav_link,
org_image_nav_name,portal_options_banner_src,portal_options_banner_link,
portal_options_banner_name,portal_options_icon_set,portal_options_support_link,
background_image_src,portal_src,portal_row_height,reg_level_ind,gateway_src,
renew_date,contact_person,contact_phone,street_1,street_2,city,state,zip,country
FROM virtual_hosts
WHERE LOWER(vhost) = ?
AND row_status = 0
ARGS: gead-black02
ERR: [Microsoft][ODBC SQL Server Driver]Communication link failure (SQL-08S01)(DBD: st_execute/SQLExecute err=-1)

And this one (I dropped the query):
execute failed: [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionWrite (send()). (SQL-01000)
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]General network error. Check your network documentation. (SQL-08S01)(DBD: st_execute/SQLExecute err=-1)

Could you please help to find where the cause of this error can be?

I'm struggling on this! Don't know where to look for anymore.

Regards,
Erico Galdino Almeida


Tatsu
Tatsu
SSCertifiable
SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)

Group: General Forum Members
Points: 6350 Visits: 307

I found this FAQ entry at 15 Seconds that recommends putting the largest column returned last in the select list. This would include making sure that text and image columns are last too.

http://www.15seconds.com/faq/ODBC/692.htm

If that doesn't work, post your connection string. I doubt this is a problem with the query (unless the above comment helps) since you're getting network-related errors. You might also need to get a Network Engineer to look at the network activity. You mentioned that the two machines were on different networks and there could be any number of problems between the two computers.

Also try searching Google for "sql server" "Communication link failure" (include the quotes). I found a bunch of things but you may find something more specific to your problem. I will keep tabs on this thread so reply after you try rearranging your query.



Bryant E. Byrd, BSSE MCDBA MCAD
Business Intelligence Administrator
MSBI Administration Blog
Erico Galdino Almeida
Erico Galdino Almeida
Old Hand
Old Hand (306 reputation)Old Hand (306 reputation)Old Hand (306 reputation)Old Hand (306 reputation)Old Hand (306 reputation)Old Hand (306 reputation)Old Hand (306 reputation)Old Hand (306 reputation)

Group: General Forum Members
Points: 306 Visits: 1

As you told me, the problem is not with the query.

I found some information and got in touch with the Network guys here.
As soon as I have a position I'll let you know.

Thank you!

Erico Galdino Almeida


Tatsu
Tatsu
SSCertifiable
SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)

Group: General Forum Members
Points: 6350 Visits: 307
Great, I hope they are able to work things out for you. If you can, share with us any troubleshooting tips you or your network folks recommend. A lot of us in this community are part of small IT organizations and where multiple hats.

Bryant E. Byrd, BSSE MCDBA MCAD
Business Intelligence Administrator
MSBI Administration Blog
Erico Galdino Almeida
Erico Galdino Almeida
Old Hand
Old Hand (306 reputation)Old Hand (306 reputation)Old Hand (306 reputation)Old Hand (306 reputation)Old Hand (306 reputation)Old Hand (306 reputation)Old Hand (306 reputation)Old Hand (306 reputation)

Group: General Forum Members
Points: 306 Visits: 1

Hello

Here I am again.
I still don't have a solution for the problem.

I found some articles that might be useful to you.
I’m trying to make this, but it still didn’t work out.

Here we go:
It describes a solution to a very similar environment of mine.
http://itsolutions.intuit.com/support/articles.asp?how=&mode=detail&kcriteria=&sVersion=&ID=254

This is the Microsoft article about the problem:
http://support.microsoft.com/kb/164167/EN-US/

Well, I changed the configuration of my ODBC connection, as told in the first link (change from TCP/IP protocol to Multiprotocol).
But every time I change it and I came back to check, the TCP/IP is the one checked.

Well, if you have any other ideas, please, let me know.

As soon as I came to a solution I’ll post it here.

Regards,

Érico Galdino Almeida


Tatsu
Tatsu
SSCertifiable
SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)

Group: General Forum Members
Points: 6350 Visits: 307

I looked a little more and found that many people have run into this problem with various DBMSs so I am pretty sure it's not a problem with SQL Server. There were a few items in the newsgroups when I searched via Google for "SQL-08S01" but most of them were either a post of the problem with no replies or not in English (French and German I think).

I am thinking this is a problem with ODBC or the network. There is a slim chance that there might be a problem with the server-side network configuration either at the ODBC layer or lower. Has your network admin checked the links between the two computers including monitoring for network saturation? I am kind of grasping at straws but I really think it's network related; either a problem or security issue of some sort.

Sorry we haven't figured this out yet!



Bryant E. Byrd, BSSE MCDBA MCAD
Business Intelligence Administrator
MSBI Administration Blog
Erico Galdino Almeida
Erico Galdino Almeida
Old Hand
Old Hand (306 reputation)Old Hand (306 reputation)Old Hand (306 reputation)Old Hand (306 reputation)Old Hand (306 reputation)Old Hand (306 reputation)Old Hand (306 reputation)Old Hand (306 reputation)

Group: General Forum Members
Points: 306 Visits: 1

Hello Bryant

I believe I solved the problem here!!!
The network guys here didn't help much, they told me everything was fine, no security issue between the two computers in the different networks. But, to tell you the truth, I don’t believe they actually tested any thing.

But, I’ve been testing our application and monitoring it in the last 7 days. We did not have the problem anymore.

Let me tell what I did:
Basically, after testing everything I told you before, I didn’t know what to do anymore. So, I read the Microsoft article once again and notice that he problem could be solved changing the default network library to Named Pipes or Multi-Protocol:

“This error may occur when the server has been set to use Integrated Security and the default network library does not support trusted connections, such as NWLink IPX/SPX, TCP/IP Sockets or Apple Talk. In this case, you will either have to configure the server for Standard or Mixed Security, or change the default network library to Named Pipes or Multi- Protocol, using the SQL Client Configuration Utility”

So, all I did was changing it again, but this time to Named Pipes and the error message still didn’t happen.

Well, I hope this can be helpful.

Thank you for your help and attention.

Best Regards,

Érico Galdino Almeida


Tatsu
Tatsu
SSCertifiable
SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)

Group: General Forum Members
Points: 6350 Visits: 307

I'm glad your issue is resolved. I wish your network people had been a little more diligent though. The problem sounds a little fishy as I have used TCP/IP for ages without any problems like that.

Thanks for keeping me posted!



Bryant E. Byrd, BSSE MCDBA MCAD
Business Intelligence Administrator
MSBI Administration Blog
JohnnyDBA
JohnnyDBA
SSCertifiable
SSCertifiable (5.7K reputation)SSCertifiable (5.7K reputation)SSCertifiable (5.7K reputation)SSCertifiable (5.7K reputation)SSCertifiable (5.7K reputation)SSCertifiable (5.7K reputation)SSCertifiable (5.7K reputation)SSCertifiable (5.7K reputation)

Group: General Forum Members
Points: 5695 Visits: 901
I'm having the same issue (and have seen it in the past at other companies).

Erico's solution doesn't really seem like a solution as much as a work around. The error is a TCP/IP specific error and by switching the protocol to named pipes you're eliminating TCP/IP out of the equation so of course it's not going to happen.

Last time I was troubleshooting this issue I was told by Microsoft to use the -g switch to increase the "memory to reserve" available to SQL Server.

Specifies an integer number of megabytes (MB) of memory that SQL Server will leave available for memory allocations within the SQL Server process, but outside the SQL Server memory pool. The memory outside of the memory pool is the area used by SQL Server for loading items such as extended procedure .dll files, the OLE DB providers referenced by distributed queries, and automation objects referenced in Transact-SQL statements. The default is 256 MB.


My particular error indicates the OLE DB provider so I'm thinking this is the issue and may also have been the original poster's issue.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum








































































































































































SQLServerCentral


Search