Solved

SQL Server [DBNMPNTW]Access denied Error

Posted on 2008-06-25
6
1,377 Views
1 Endorsement
Last Modified: 2012-05-05
I moved a SQL Server 2000 db on Windows 2000 to a Windows 2003 server using SQL Server 2005.  I have 5 load-balanced web servers hitting this db.  Users are getting an intermittent error:

Microsoft OLE DB Provider for SQL Server error '80004005'
[DBNMPNTW]Access denied.

I am only seeing this error a few times an hour which makes it hard to reproduce.
1
Comment
Question by:ifcosystems
  • 3
  • 3
6 Comments
 
LVL 32

Expert Comment

by:Daniel Wilson
ID: 21866351
Try using SQL Profiler to trap & log Failed Login Attempts.

This should tell you:
* Who
* what program
* What computer

That should get you close to solving it ... hopefully!
0
 

Author Comment

by:ifcosystems
ID: 21866590
I noticed the old Windows 2000/SQL Server 2000 had the protocols TCP/IP and Named Pipes enabled.  The new server only has TCP/IP enabled.  Could that have anything to do with it?
0
 
LVL 32

Expert Comment

by:Daniel Wilson
ID: 21866701
doubtful.

It looks like a permissions issue.
0
Free learning courses: Active Directory Deep Dive

Get a firm grasp on your IT environment when you learn Active Directory best practices with Veeam! Watch all, or choose any amount, of this three-part webinar series to improve your skills. From the basics to virtualization and backup, we got you covered.

 

Author Comment

by:ifcosystems
ID: 21866930
Hopefully I'm on to something...If you look at http://support.microsoft.com/kb/238949, it says DBNMPNTW is for named pipes.  Since I have that disabled on the SQL Server, wouldn't that be the reason for the error?  And the reason that some users are connecting and some are not could be that most of the web servers are using dbmssocn (TCP/IP), but sometimes they are using DBNMPNTW.  Make sense?  Then the question becomes why is DBNMPNTW being used sometimes?  The 5 web servers are using asp pages that use a UDL to connect.  I don't know how the UDL determines which network library to use.
0
 
LVL 32

Expert Comment

by:Daniel Wilson
ID: 21867096
Maybe ... won't hurt to give it a try!
0
 

Accepted Solution

by:
ifcosystems earned 0 total points
ID: 21869127
I solved this:  Turns out one of my servers is using MDAC 2.53.6200, who's default behavior is to use named pipes.  I changed the connection string on this server to use dbmssocn (TCP/IP), and all is well.  Give me 500 points!
0

Featured Post

Connect further...control easier

With the ATEN CE624, you can now enjoy a high-quality visual experience powered by HDBaseT technology and the convenience of a single Cat6 cable to transmit uncompressed video with zero latency and multi-streaming for dual-view applications where remote access is required.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

We recently endured a series of broadcast storms that caused our ISP to shut us down for brief periods of time. After going through a multitude of tests, we determined that the issue was related to Intel NIC drivers on some new HP desktop computers …
This article explains how to reset the password of the sa account on a Microsoft SQL Server.  The steps in this article work in SQL 2005, 2008, 2008 R2, 2012, 2014 and 2016.

820 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question