Weird SQL Server problem
-
Hi,
Since yesterday, I experiment a problem connecting with a SQL Server
2000 database. The DB is located in a server (Win2000 Server). Our
software (designed with VB.NET 2003) connect to this DB for the
production, is installed on a WinXP SP2 IBM PC. But now, I get the
error: "Unable to load SQL Server OLEDB provider resource DLL. The
application cannot continue" every time I load the software. It always
worked, but since yesterday, it doesn't anymore.
An another program, designed in VB6, in installed on the same PC and
connect to the same DB, and it works fine.
Many others PC (XP and 2000), with differents softwares designed in
VB6, connect with that same server/DB and it also works fine.
So I moved the DB to another server. And the software, who could not
connect with the original server, connect successfully!! When I try
back to connect with the first server, it still give that annoying
"unable to load blah blah blah" error message. But it works with
another server...
That same software is installed on another computers. And it works
fine.... (???!!!!). So I tried to install the program in a new Win2000
PC. When I try to connect with the first server, I get the error
message. When I connect to the backup server, it works fine.
I have absolutly no damn idea what the hell is going on... any idea
someone??
thanks a lot for your time and help, it's really appreciate..
-
Are both applications using the OLEDB driver, or is one using ODBC and the other OLE? Was a security patch deployed yesterday or the day before? If so what was it?
You said you got it to work with your backup server... is the backup server the same patch level for the OS and for SQL?
When you open the SQL client Network Utility on both servers, are all of the same settings there? Did someone perhaps change one on your production server?
If the .Net application is one that's currently in development, can you roll back to older code and look at what may have changed?
-Luke.
P.S also as a side note, I can understand your frustration with this issue, but your second to last sentence might have been a bit over the top for a public site. I believe your frustration could have been conveyed without the expletives.
-
Both servers are exactly similar. Same setup, same patched, same version. Network Utility shows the same result. No patch deployed on the servers wathsoever. I tried to reinstalled MDAC 2.8, giving full control on SQLOLEDB.DLL and SQLOLEDB.RLL to Everyone. Both files have the same version. I rebooted the PC and the server. Nothing works. Still get that annoying message. What I founded out, the program can connect with the DB, it's when it executed StoredProc that I get this error pop-up. On the backup server, everything works fine.
Yet, the software is installed on 4 others computers and it works with the master server. Same software, same PC's (configured exactly the same). On my laptop when executing the program from Visual Studio, works fine too.
I tried to install the program on a new Win2000 PC. Same thing. get the pop-up error when I connect with the master server. Works fine on the backup.
I'm really, really confused by this one...
any idea? thanks for your help
- Dominic
PS: Sorry for the expletives. I'll be carefull in the future.
-
I take it there ar eno error messages in the event log of the server or Workstation. Nothing in the SQL logs as well. Can you log into the other workstations the same way as on your laptop and log into your app the same way and have it work? Seems this could be some sort of strange permissions thing. At least that's what it seems like on the surface.
-
nope, no entry in the event logs at all. The other workstations use the same Windows user and the same SQL user and both servers have the same rights/permissions configured (they are identical, same hardware, same settings).
I'm really confused...
-
Dollars to donuts says that someone change the privs on a folder or deleted a user with the privs... did you do a search for the DLL to find out where the hell it is?
--Jeff Moden
RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.Change is inevitable... Change for the better is not.
Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally) -
the SQLOLEDB.RLL and SQLOLEDB.DLL are in the correct folder, correct version (MDAC 2.8), and the folder have all privs for everyone. I think we'll rebuild the box from scratch, we just could not found where the problem comes from.
I love computers.....
-
I'm with you there... one of my favorite sayings is "Anyone can make a mistake but to really mess things up, you need a computer."
--Jeff Moden
RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.Change is inevitable... Change for the better is not.
Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)
Viewing 8 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply