Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
robg69
Starting Member
41 Posts |
 Posted - 2003-07-02 : 11:57:04
|
| Hey Guys, does anyone know what this error means:[Microsoft][ODBC Driver Manager] Driver's SQLAllocHandle on SQL_HANDLE_ENV failedWindows 2000 ProSQL Server 2000Mdac 2.6, etcWe are getting this error on a computer here when we try to login with Enterprise Manager. So we tried uninstalling and reinstalling Enterprise Manager, but it did not work. Also, we haven't installed any new software on the computer or anything like that. It just started happening yesterday. Anyone have a clue what would cause this, we can wipe and reload the machine, but if we can avoid that, we would like to.Thanks!-Rob |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-07-02 : 12:14:38
|
| I have never seen that error message before. I'd though that I'd seem them all from my last job (bad network problems so we pretty much saw every SQL connection error), but this one is new to me. Does Query Analyzer work? Does the error only occur when you try to connect to a server? Is it only a specific server? Have you tried connecting to another server? How about rebooting (though I'd ask)? I would suggest searching for your error (search on this part: Driver's SQLAllocHandle on SQL_HANDLE_ENV failed) in MS' knowledge base: [url]http://support.microsoft.com/[/url]I searched the knowledge base, but it returned a lot of articles and I don't know anything about that computer or environment, so you'll need to go through the articles.Tara |
 |
|
|
robg69
Starting Member
41 Posts |
Posted - 2003-07-02 : 12:22:07
|
| No, Query Analyzer doesn't work either. I've searched high and low on google and M$'s support site with no results except problems relating to connections with Oracle (which isn't are problem). Thanks,-Rob |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-07-02 : 12:28:17
|
| Have you tried reloading MDAC? I would do that before I considered rebuilding the machine. Also try reapplying the Windows service pack. BTW, what service pack of SQL Server is the client machine running? A lot of people don't install the service packs on the client machine, but you might consider it considering the problem that you are encountering. I would suggest service pack 2 or service pack 3a for SQL Server.Tara |
|
|
|
robg69
Starting Member
41 Posts |
Posted - 2003-07-02 : 12:57:05
|
OK, well I seemed to have figured out the problem. I replaced a few ODBC dlls and the SQL Server dll: sqlsrv32.dll with newer versions and re-installed the SQL Server client tools and it seems to be working now. We had mdac 2.6 and W2K SP3 on there already. Weird.Oh well, thanks for attemping help.  -RobP.S. Thanks Tara, I think reinstalling mdac 2.6 and SQL Server SP3 would probably be the best thing to do. Edited by - robg69 on 07/02/2003 12:59:55 |
|
|
|
|
|
|
|
|
Strange Error trying to enter Enterprise Manager