This is a discussion on RE: Upgrading to MDAC 2.7sp1 causes SQL to fail within the MS SQL ODBC forums, part of the Microsoft SQL Server category; --> Do you have clustered SQL Server 7.0 or a non-clustered ? NOTE: MDAC 2.6 or Later Should Not Be ...
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Do you have clustered SQL Server 7.0 or a non-clustered ? NOTE: MDAC 2.6 or Later Should Not Be Installed on SQL Server 7.0 Clusters http://support.microsoft.com/?id=820754 Does your machine have the file "sqlwoa.dll" ? If yes, what is the version, size and location/s ? What is the exact error message that you get ? What are the messages that get logged in SQL Server Agent log (sqlagent.out) ? Regards, Uttam Parui SQL Server Developer Support Engineer, MCDBA, MCSE, MCT Product Support Services Microsoft Corporation This posting is provided "AS IS" with no warranties, and confers no rights. Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security. |
| |||
| I have NON-clustered SQL 7.0 sqlagent.out does not exist sqlwoa.dll does not exist in order to get these files back I uninstalled SQL 7.0 then reinstalled it. After reinstalling I get sqlwoa.dll with a size of 49 KB and modified date of October 20, 1999. After reinstalling I run comcheck and it appears that I have more than one version of mdac. Then I run comcheck /d reconfigure mdac to install mdac 2.71sp1. COM check indicates that the install was successful. When I run COM check again after this upgrade, I seem to have more than one version of mdac. After this, sqlagent.out does not exist and sqlwoa.dll does not exist and when I run iSQL or SQLagent.exe I get the message sqlwoa.dll could not be found in the specified path. Therefore, it seems that upgrading to mdac 2.7sp1 deletes files that are necessary for SQL 7.0. What should I do? I recently purchased SQL2000 and eventually plan to upgrade to SQL 2000. If I upgrade to SQL 2000 will this fix the problem? I've also purchased Windows 2000 server and plan to upgrade my Windows NT 4.0 server. However, I thought that I should get these problems fix before doing upgrades. Should I? "Uttam Parui[MS]" <uttamkp@online.microsoft.com> wrote in message news:34mWA1vYDHA.2108@cpmsftngxa06.phx.gbl... > Do you have clustered SQL Server 7.0 or a non-clustered ? > > NOTE: MDAC 2.6 or Later Should Not Be Installed on SQL Server 7.0 Clusters > http://support.microsoft.com/?id=820754 > > Does your machine have the file "sqlwoa.dll" ? If yes, what is the version, > size and location/s ? > > What is the exact error message that you get ? > > What are the messages that get logged in SQL Server Agent log > (sqlagent.out) ? > > Regards, > > Uttam Parui > SQL Server Developer Support Engineer, MCDBA, MCSE, MCT > Product Support Services > Microsoft Corporation > > This posting is provided "AS IS" with no warranties, and confers no rights. > > Are you secure? For information about the Strategic Technology Protection > Program and to order your FREE Security Tool Kit, please visit > http://www.microsoft.com/security. > |
| ||||
| From your description it appears that installing mdac 2.7 sp1 from com check, the file sqlwoa.dll is getting deleted. I have MDAC 2.7 SP1 on my server but that was installed by SP3 for SQL 2K. My server has both SQL 7.0 and SQL 2K. SQL Agent 7.0 works fine. Since you know that by installing mdac 2.7 sp1 using com check you are having this problem, I would recommend not to install mdac 2.7 sp1 now. Upgrade to Win 2K and SQL 2K first and then install the latest SP for SQL 2K (i.e SP3a and you will have MDAC 2.7 SP1 + plus some other mdac fixes). HTH, Uttam Parui SQL Server Developer Support Engineer, MCDBA, MCSE, MCT Product Support Services Microsoft Corporation This posting is provided "AS IS" with no warranties, and confers no rights. Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security. |