Connection to SQL file *.MDF requires SQL Server 2005 to function properly.

PROBLEM DESCRIPTION
============================================
Getting below error message while trying to add Data from SQL Express 2008 DB through Visual studio 2008

ERROR MESSAGES:
============================================
Connection to SQL file *.MDF requires SQL Server 2005 to function properly.

Environment:
============
64 bit SQL Server
64 bit OS
32 bit Visual studio

Reference Links
============================================
http://blogs.msdn.com/sqlexpress/archive/2008/10/02/faq-error-creating-a-service-based-database-in-visual-studio-2008-sp1.aspx
http://support.microsoft.com/KB/957944

Resolution:
=============
Apply the hot fix mentioned in this KB http://support.microsoft.com/KB/957944

System.Runtime.InteropServices.COMException (0x800706B3)

Problem Description:
=======================================================================
Throwing the below error while setting the web service identity in configure report server

System.Runtime.InteropServices.COMException (0x800706B3)
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at System.Management.ManagementObject.Get()
at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.SetDatabaseConnection(String server, String database, ConfigurationCredentialsType credsType, String userName, String password)

Troubleshooting steps:
=======================================================================
Checked the reporting services configuration server.

Execution account was enabled. Unchecked it; Specify an execution account checkbox should not be checked.

Created new report server virtual directory and report manager virtual directory through the reporting services configuration server tool.

Windows service identity was set to built in account --- Network service

In Webservice identity; created new app pools for Report Server and Report Manager using reporting services configuration server tool.

If while creating new app pools you get the above error go to encryption keys and hit on delete button.

Once encryption keys are deleted Try recreating the app pools once again and it should create fine without any errors

Resolution:
=======================================================================
Reports coming up fine when we browse http://localhost/reportserver and http://localhost/reports

SQL Server does not exist or access denied.

Cause:
=======================================================================
Not enabled protocols on SQLExpress box as well as client box
Firewall blocking issue of port and service

Resolution:
=======================================================================
1. Checked the protocols whether its enabled
2. Ran the command cliconfg from start---Run on local box and enabled both tcp/ip and named pipes
3. Done the same on the SQLExpress box
4. went to SQLServer 2005 Surface area configuration and changed the services and connections set the local and remote connections to use both tcp/ip and named pipes
5. Typed in start---run----firewall.cpl
6. Went to exceptions tab and added the following services to it
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\sqlservr.exe executable program
C:\Program Files\Microsoft SQL Server\90\Shared\sqlbrowser.exe executable program
7. Add the port of SQLExpress 1433 to exception list
8. Restarted the service
9. browsed the application and it was working fine without any errors.

Cannot generate SSPI context

How to troubleshoot the "Cannot generate SSPI context" error message
http://support.microsoft.com/kb/811889

Usually this drills down to improper SPN [Service principal Name] Not registered properly

Related Knowledge Base Articles
===========================
Troubleshooting Kerberos Errors
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/security/tkerberr.mspx

How to enable Kerberos event logging
http://support.microsoft.com/kb/262177

How to troubleshoot the "Cannot generate SSPI context" error message
http://support.microsoft.com/kb/811889

How to make sure that you are using Kerberos authentication when you create a
remote connection to an instance of SQL Server 2005
http://support.microsoft.com/kb/909801/en-us

Security Account Delegation
http://msdn2.microsoft.com/en-us/library/aa905162(SQL.80).aspx

SQL Linked Server Query failed with “Login failed for user …”
http://blogs.msdn.com/sql_protocols/archive/2006/08/10/694657.aspx

Windows 2000 Resource Kit Tool : Setspn.exe
http://www.microsoft.com/downloads/details.aspx?FamilyID=5fd831fd-ab77-46a3-9cfe-ff01d29e5c46&displaylang=en

Windows Server 2003 Service Pack 2 32-bit Support Tools
http://www.microsoft.com/downloads/details.aspx?FamilyID=96a35011-fd83-419d-939b-9a772ea2df90&DisplayLang=en

An internal error occurred on the report server.

Problem Description:
=======================================================================
Older 2000 server and wanting to move reporting services to SQL 2005
An internal error occurred on the report server. See the error log for more details. (rsInternalError) Get Online Help Key not valid for use in specified state.

Steps:
=======================================================================

1. From Explorer, navigate to x:\Documents and Settings\\Application Data\Microsoft\Crypto\RSA\S-1-5-20. In this case, the folder was C:\Documents and Settings\NetworkService\Application Data\Microsoft\Crypto\RSA\S-1-5-20.

2. Search for files with the pattern "1aedd7b5699f3d6a88e354100b596aae_*". These files represent the Microsoft SQL Server Reporting Services Key Container.
3. Delete these files.

Removing encrypted content, reconfiguring the SQL Server login account, and activating the report server:
rskeymgmt.exe -d
rsconfig.exe -e -s -d -a Windows -u -p -t
now restarted the service

Browsed the reports it works fine.

Restored the backup DB of reportserver and reportservertempdb on the dc02 box

Now pointed the reports to fetch the data from the DC02 Machine using the below command.

rsconfig -c -m -s -d reportserver -a SQL -u SA -p

Resolution:
=======================================================================
Now able to browse the reports after success fully migrating from 2000 to 2005.

Unable to install SRS2000; Error code 1603

Problem Description:
=======================================================================
Unable to install SRS2000; Error code 1603

Cause:
=======================================================================
Not properly removed the SRS2000.
Need to manually reconfigure it.
Done the below steps as mentioned in the resolution.

Resolution:
=======================================================================
Checked for all the below ones and manually made sure that they are deleted
a. Default locations:
i. C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services
ii. C:\Program Files\Microsoft SQL Server\80\Tools\Report Designer
iii. C:\Program Files\Microsoft SQL Server\80\Tools\Reporting Services
b. Remove tools items (C:\Program Files\Microsoft SQL Server\80\Tools\Binn)
i. ReportingServices.mof
ii. Rs.exe
iii. RSConfig.exe
iv. RSActivate.exe
v. RSKeyMgmt.exe
vi. ReportingServicesWmi.dll
vii. Resource folders
1. All Languages (DE, ES, etc)
2. 1033
4) Made sure the Virtual Directories were removed.
Removed Report Server dlls
5) Removed Registry Entries
a. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\80\Reporting Services
6) Made sure the Databases were removed.
a. Default names are ReportServer and ReportServerTempDB

After that, we were able to install Reporting Services successfully after following the above steps.

SQLState: S0001, Message: The server failed to resume the transaction. Desc:3600000000

Problem Description:
=======================================================================
When web based java application is connecting to SQL server 2005 backend through JDBC, they are getting error message
SQLState: S0001, Message: The server failed to resume the transaction. Desc:3600000000., Vendor Error Code: 3971

Cause:
=======================================================================
Here are the scenarios that you might get this error message (“failed to resume the transaction”):
• A nested stored procedure is called
• Stored procedure returns output parameters
• A deadlock occurs. After waiting, the stored procedure is executed again and receives "failed to resume transaction"

Workaround/Resolution:
=======================================================================
Here is some of the work around being prescribed since we have started seeing the issue:
1) Use PreparedStatement in lieu of Statement. This ensures that outstanding TDS packets are parsed when close() is called.
2) Call Statement.getMoreResults() and Statement.getUpdateCount() until those functions indicate there are no more results to be processed. This ensures that all outstanding TDS packets are parsed.

Questions on Subscriptions and Jobs in SSRS

Articles:
=======================================================================
http://msdn2.microsoft.com/en-us/library/aa237763(SQL.80).aspx---Managing Subscriptions
http://msdn2.microsoft.com/en-us/library/aa237786(sql.80).aspx---Subscription Overview
http://msdn2.microsoft.com/en-us/library/aa237767(SQL.80).aspx---Creating, Modifying, and Deleting Subscriptions
http://msdn2.microsoft.com/en-us/library/aa237758(SQL.80).aspx---Using Role-Based Security
http://msdn2.microsoft.com/en-us/library/aa225485(SQL.80).aspx---New Role Assignment / Edit Role Assignment Page


http://msdn2.microsoft.com/en-us/library/ms190387.aspx---User-Schema Separation
http://msdn2.microsoft.com/en-us/library/ms188676.aspx---Ownership Chains

Failed to map the path '/YourApplication/App_GlobalResources'

Problem Description:
=======================================================================
Failed to map the path '/YourApplication/App_GlobalResources'.

Troubleshooting Steps:
=======================================================================
Step 1:
=============
In the folder --> C:\Documents and Settings\All Users\Application Data\Microsoft\Crypto\RSA\MachineKeys
... checked for the key that was 0 KBytes, but none was there if any 0 kb keys we need to delete it

Step 2:
==============

Run the aspnet_regiis utility in the framework folder:

c:\WINNT\Microsoft.NET\framework\v2.0.50727\aspnet_regiis -i

This will re-register ASP.NET with IIS and re-create the ASPNET account.

Next you need to give permissions to the (nicely refreshed) ASPNET user account to access this folder with Modify permissions:

C:\Documents and Settings\All Users\WINNT\Application Data\Microsoft\Crypto\RSA\MachineKeys

Restart of IIS

Step 3:
===========
Click the Security Tab under the Properties of the C:\Documents and Settings\All Users\Application Data\Microsoft\Crypto\RSA and add the ASP.NET account with full control

Now it was throwing reportserver.config denied

Gave aspnet permissions on that file that resolved the access denied error

Now it was throwing reportserver not found error

Checked rswebapplication.config and changed the URL
Added reporserver element between reportservervirtualdirectory
Now reset the IIS. Restarted the reporting services

Now browsed the reports and reportserver from IIS as well as URL
It was working fine.

RS server configuration error access to path c program file MS SQL server MSSQL.2/Reporting services report server RS report server .config is denied

Problem Description:
=======================================================================
RS server configuration error access to path c program file MS SQL server MSSQL.2/Reporting services report server RS report server .config is denied

Troubleshooting steps:
=======================================================================
Ran process Monitor tool
Found that aspnet_wp.exe has access denied on the path specified
C:\Program Files\Microsoft SQL Server\MSSQL.2\Reporting Services\ReportServer\RSReportServer.config [Access denied]
Gave the network service permissions on the reporting services folder
Restarted the IIS
This resolved the issue.

The report server installation is not initialized. Check the documentation for more information. (rsReportServerNotActivated)

Problem Description:
=======================================================================
The report server installation is not initialized. Check the documentation for more information. (rsReportServerNotActivated) Get Online Help -2147159549
0x80090005

Cause:
=======================================================================
Keys Corrupted

Resolution:
=======================================================================
Ran rskeymgmt –d
Ran rsconfig and rsactivate commands
Now able to browse the reports and reportserver.

The report server cannot open a connection to the report server database. The logon failed (rsReportServerDatabaseLogonFailed). Logon failure: unknown

Problem Description:
=======================================================================
"The report server cannot open a connection to the report server database. The logon failed (rsReportServerDatabaseLogonFailed). Logon failure: unknown user name or bad password."

Cause:
=======================================================================
Not configured properly rsreportserver.config

Resolution:
=======================================================================
Run the Rsconfig command rsconfig -c -s -d ReportServer -a windows -u -p
Run the Rsactivate.exe -c "c:\programfiles\microsoft sql server\mssql\reporting services\reportserver\rsreportserver.config"
Reset the iis and service of reportserver

Not getting any errors, but also not getting button to launch the Report Builder.

Problem Description:
=======================================================================
Not getting any errors, but also not getting button to launch the Report Builder.

Cause:
=======================================================================
Doesn’t have sufficient permissions for the user.

Resolution:
=======================================================================
Solution1:

Users cannot see the Report Builder icon unless they are in the local Administrators group. Users need to be in the site-wide System User role in order to run Report Builder. This role adds the "Execute report definition" task, which is only included in the System Administrator and System User roles.

Solution2:

Tutorials on MSDN and adding the users to just the reporting server via SQL Mgmt Studio.
http://msdn2.microsoft.com/en-us/library/aa337469.aspx

"An error occurred during printing (0x80004005)" while printing second page

"An error occurred during printing (0x80004005)" while printing second page

Resolution:
============
Checked the enterprise manager ----Databases -------ReportServer-------Tables--------ConfigurationInfo

===>Changed the UseSessionCookies value to "true" inside the ConfigurationInfo table of the ReportServer database
===> Reset IIS

Unable to start T-SQL Debug. Failed to attached the SQL Server process

Below Info provided could help you to resolve the issue.

http://msdn2.microsoft.com/en-us/library/s0fk6z6e(VS.80).aspx

http://msdn2.microsoft.com/en-us/library/s4sszxst(VS.80).aspx

http://msdn2.microsoft.com/en-us/library/ms165038(VS.80).aspx

http://msdn2.microsoft.com/en-us/library/s7ahaxtd.aspx to ensure that you have the permissions and your setup is fine.

SQL Scenario: One or Both machines is in a workgroup

Create the same local user on both machine e.g. SQLUser, ensuring that they have the same password.
Then also set the SQL Server Service to run as SQLUser

817178 Troubleshooting tips for T-SQL Debugger in Visual Studio .NET
http://support.microsoft.com/default.aspx?scid=kb;EN-US;817178

-Though for VB, this article has some useful suggestions: 170496 INF: Tips for Debugging Stored Procedures from Visual Basic
http://support.microsoft.com/default.aspx?scid=kb;EN-US;170496

MSDN Forums here is the link http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=587959&SiteID=1

TQL-Debugging is a feature only supported in VS .NET Enterprise addition per http://msdn2.microsoft.com/en-us/library/aa290350(vs.71).aspx#vstchdebugginginvisualstudionetanchor6

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dv_vstechart/html/vsdebug.asp

http://support.microsoft.com/?kbid=896861

http://ryanfarley.com/blog/archive/2005/08/23/8540.aspx

I was having the “Unable to Start Debugging on the Web Server” error on my localmachine when debugging simple local aspx apps (not web services). My initial resolution attempts included everything outlined under "Initial Attempts," and even reinstalling Visual Studio .NET and the .NET Framework 1.1 and 2.0 failed. But read on; I stumbled across a solution that might work for some of you.

Initial Attempts (taken from previous posts)
----------------------------------------------------
(1) Make sure that IIS is configured to use Integrated Windows Authentication. Look for the checkbox on the Authentication Method dialog launched from the Directory Security tab of the site properties.

(2) Make sure that HTTP Keep Alives are enabled. You'll find that checkbox on the Web Site tab of the properties dialog, in the connections section.

(3) This one is strange, but it seemed to do the trick for many out there, add the trusted sites in Internet Explorer. To tell the truth, this seems to be a fix for the symtoms, not actually fixing the problem itself, but if it works it works. BTW, you'll have to uncheck the “Require server verification (https:) for all sites in this zone“ checkbox to add it as a trusted site.

The Fix
----------------------------------------------------
(4) In IIS on the local machine, I brought up the web site properties. Under the tab labeled ASP.NET, I was using 2.0.5072. When I reverted back to version 1.1.422, the debug problems went away.

SQL Server 2005 Debugging Requirements
There have been some questions about the sysadmin requirement of SQL Server 2005 Debugging, and I’d like to explain it in some details. When you debug T-SQL or CLR code in SQL Server 2005, there are two users involved: user running the debugger and user making the connection that is being debugged. User running the debugger (Visual Studio 2005) has to be in the sysadmin fixed role, and there’s no requirement on the user making the connection. Also because Visual Studio communicates with SQL Server through debugging interfaces in DCOM, the debugger user has to use Windows Authentication rather than SQL Server Authentication.
For CLR code debugging, sysadmin is required because CLR debugger user has total access to the memory of SQL Server process, and we don’t want anyone other than sysadmin to have it.
For T-SQL debugging some alternatives have been considered. One alternative is to allow anyone to debug T-SQL procedure/function that s/he has certain permission (e.g. alter permission or ownership). This would be much more convenient for developers, but it has some security complications, especially in cases like procedure with EXECUTE AS and signed procedures. Also filtering of T-SQL stack frames based on permissions make implementation more complex. We gave up on this for SQL Server 2005, and will reconsider it for future versions. Another alternative is to make execute permission on sp_enable_sql_debug grantable and allow anyone with this permission to debug T-SQL. After security review we found that without solving security problems that prevented us from the first alternative, it’s possible for a malicious debugging user to elevate to sysadmin privilege. Thus debugging permission is equivalent to sysadmin privilege and we chose to signify this by only allowing sysadmin to execute sp_enable_sql_debug.
Remote Debugging Monitor (msvsmon.exe) is another requirement that people often get confused on. Remote Debugging Monitor is required for SQL-CLR debugging, whether remotely or locally (here are the steps to set up the Remote Debugging Monitor); and it is not required for T-SQL debugging, whether remotely or locally. Here “local” means Visual Studio 2005 and SQL Server 2005 run on the same machine.
For T-SQL debugging Visual Studio doesn’t actually attach to the SQL Server process. It communicates with SQL Server through a set of debugging interfaces in DCOM, so msvsmon.exe is not required. For SQL-CLR debugging msvsmon.exe is required even for local debugging for robustness reasons. In this case msvsmon.exe attaches to the SQL Server process, and Visual Studio talks to msvsmon.exe through some private channels. In this way even if Visual Studio crashes or freezes, msvsmon.exe can detect it and detach safely from SQL Server process. If Visual Studio attaches to the SQL Server process directly, and something bad happens to Visual Studio, then SQL Server process can be terminated, which is what we try to avoid. Msvsmon.exe is relatively small and we can make it pretty robust; whereas Visual Studio is much more complex and has open plug-in architecture, and thus is much more susceptible to problems.

installations of SSRS 2005

Good Link to follow

http://www.mathgv.com/sql2005docs/SQL2005ReportingServicesInstall.htm

A transport-level error has occurred when sending the request to the server. (provider:tcpprovider, error:0-existing connection was forcibly closed by

ERROR MESSAGES:
============================================
A transport-level error has occurred when sending the request to the server. (provider:tcpprovider, error:0-existing connection was forcibly closed by remote host)

Resolution:
=========
Most of the times issue is Figured out to be a network device issue

using windows server 2003 and Broadcom network card

apply this KB

http://support.microsoft.com/default.aspx?scid=kb;EN-US;942861

SQL Linked Server Query failed with “Login failed for user …”

Good Blog for Trouble shooting the above error message

http://blogs.msdn.com/sql_protocols/archive/2006/08/10/694657.aspx

SQL Server Management studio we don’t find any SSIS folders

PROBLEM DESCRIPTION
============================================
while expanding SQL Server Management studio we don’t find any SSIS folders as required.

Resolution:
=======================================================================
checked MsDtsSrvr.ini.xml,
Replace with original content with default.
if you have any other file MsDtsSrvr.ini.xml on any other box compare it.
This resolved the issue

Database Login failed:Failed to connect to SLXServer.

ERROR MESSAGES:
============================================
Database Login failed:Failed to connect to SLXServer. Check if the server is running and is compatible with the current provider version

Resolution:
============
http://www.slxdeveloper.com/forum.aspx?forumid=3000&postid=11806

Possible Resolution 1:
Delete and recreate the database and datalink connections. For more information see, How to delete and recreate the datalink and database connections.
Possible Resolution 2:
Verify Windows Firewall is set to allow SLXSystem.exe as an allowed Exception. If not, select to allow it and reboot the machine.
Possible Resolution 3:
Restart the SalesLogix services. For more information see, How to stop and restart the SalesLogix services.
Possible Resolution 4:
Add Server IP address to the system32 host file since DNS is not being used.Note: Refer to Microsoft's Knowledge Base for information on updating Windows System32 host files.
Possible Resolution 5:
Uninstall and reinstall SalesLogix. For more information see, How to uninstall and reinstall SalesLogix.
Possible Resolution 6:
Reboot the computer(s) experiencing this error.
Possible Resolution 7:
Check the version of the executables for SalesLogix and the bundles that are installed. The version map is available on Support Online for more information as to what version of executables are for which version of SalesLogix.
Possible Resolution 8:
Check network connectivity on the effected workstation. The error can be recieved with a network failure or a failing NIC (network adapter) causes a workstation to be isolated from the client's network.
Possible Resolution 9:
Start the COM+ Objects. For more information, see How to start and stop COM+ Objects.

Frequently asked questions about the installation of Microsoft Data Access Components (MDAC)

http://support.microsoft.com/kb/842193

What can I do if I must roll back to an earlier version of MDAC?

Caution Rollback might cause pre-existing applications to function incorrectly.

To initiate Rollback, run the Dasetup.exe file with the following command line:dasetup.exe /uNote The Dasetup.exe file is already installed on the computer.

we cannot add new ODBC connections to sql server

PROBLEM DESCRIPTION
============================================
we cannot add new ODBC connections to sql server

ERROR MESSAGES:
============================================Connection Failed:SQLState:'01000'SQL Server Error:2[Mirosoft][ODBC SQL Server Driver[Named Pipes]ConnectionOpen(Connect()).Connection failed:SQLState:'08001'SQL Server Error: 17[Microsoft][ODBC SQLServer Driver][Named Pipes]SQL Server does not exist or access denied.

Resolution:
=========
Check on which port is SQL Server Listening on
if the SQL Server is not listening on Default port
Make the Server alias To Listen on right port on which SQL is listening
Run CLICONFG from Start -- Run Command

System.Runtime.InteropServices.COMException (0x80040427): Execution was canceled by user.

Problem Description:
=======================================================================
SSIS package which runs a DTS package using the execute DTS2000 component.Able to run the package in the standalone server but on the cluster getting following error
Error: System.Runtime.InteropServices.COMException (0x80040427): Execution was canceled by user. at DTS.PackageClass.Execute() at Microsoft.SqlServer.Dts.Tasks.Exec80PackageTask.Exec80PackageTask.ExecuteThread()

Resolution:
=============
Check the ODBC DSN Connection if its proper

How to Uninstall/Reinstall MDAC

1. Remove the MDAC Exception component keys from HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\ExceptionComponents.
2. Re-run the MDAC 2.81 installer (MDAC_TYP.EXE) or Anyother MDAC Components installer. http://www.microsoft.com/downloads/details.aspx?familyid=78cac895-efc2-4f8e-a9e0-3a1afbd5922e&displaylang=en

MDAC Will be Fixed.
To Make sure MDAC is fixed run below Tool
http://www.microsoft.com/downloads/details.aspx?FamilyId=8F0A8DF6-4A21-4B43-BF53-14332EF092C9&displaylang=en

For windows XP

IF ERROR IS THIS

This setup does not support installing on this operating system.

http://support.microsoft.com/kb/899861

I had a similar experience. Two possible options can be used to allow XP to repair the entries or force the install without having to repair the XP installation.

1. To repair your MDAC installation. Found this solution on the web that works. Have your XP SP2 install disk handy. Go to and find c:\windows\inf\mdac.inf. Right click on the .inf file and pick Install. It will attempt to reinstall the files. Browse to source files on the XP CD. It should install smoothly. It may ask for the handler.reg (in c:\program files\common files\system\msadc\). Restart. Sign in (admin) and then after a few minutes windows update will want to apply the security patch again. You may want to follow up with the SJet update also.

2. To force the installation. Found this one also. XP SP2 will already have the SP1 update applied but has registry corruption (virus after affects). Right click on the MDAC 2.8 SP1 install exe file and select properties. Select the Compatability tab, check the compatability mode box and pick "windows NT" or possibly "Windows 2000". Click apply and run the file again. It should install all the proper files again.



MDAC Component Checker Details
http://support.microsoft.com/kb/307255

ELSE

1. Download the MDAC version you want on the box from:
http://www.msdn.microsoft.com/data/mdac/downloads/default.aspx

2. Open the registry editor by entering the following at a command prompt:
regedit

3. Navigate to the following hive and delete the exception components:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\ExceptionComponents

Note: this prevent you from overwriting MDAC is they exist therefore they need deleted.

4. navigate to the following hive HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DataAccess

and set the following key to the following value: FullInstallVer, RollbackVersion, and Version to 2.60


Note: when MDAC checker it will see it's old and allow the upgrade to 2.6 SPx or higher


5. Disable anti-virus(very important), stop services such as SQL server, IIS, etc., close applications

6. Run the MDAC_typ.exe from step 1 above to install they version on the box.

7. Reboot and verify the install by running the MDAC Component checker downloadable from

http://www.msdn.microsoft.com/data/mdac/downloads/default.aspx

OR try

1. Windows operating system repair to get to the RTM release of MDAC.

2. Download the version he wanted on the box from http://msdn.microsoft.com/data/mdac/downloads/default.aspx

3. Disable Anti-virus(VERY IMPORTANT), close all applications, stop services such as SQL and IIS, then run the MDAC_tpy.exe for the version downloaded in step 2 above to install it.

4. Verify the install via the MDAC Component Checker also on http://msdn.microsoft.com/data/mdac/downloads/default.aspx

5. Apply Windows updates and hotfixes.

The setup routines for the SQL Server ODBC driver could not be loaded due to system error code 126.

PROBLEM DESCRIPTION
============================================
Creating ODBC Connection Using DSN and getting this error

ERROR MESSAGES:
============================================---------------------------
Microsoft ODBC Administrator
---------------------------
The setup routines for the SQL Server ODBC driver could not be loaded due to system error code 126.
---------------------------
OK
Resolution:
=======================================================================
Sqlsrv32.dll file missing from the c:\windows\system32 folder
Copying Sqlsrv32.dll file resolved the issue.