Vidhya Sagar – Blog

This is a quick post to install or enable .Net 3.5 on windows 7. Last couple of weeks I’m seeing more questions on installing SQL Server 2008 in windows 7 and the users are unable to install SQL Server 2008 pre-requisite (.Net 3.5 ). To Install SQL Server 2008, windows installer 4.5 & .Net 3.5 is required. Windows installer 4.5 is installed and enabled by default, .Net 3.5 is included in windows features, so you can directly go there and turn on .Net 3.5, windows 7 will automatically install this. To turn on .Net 3.5  in Windows 7 just follow the steps below

Read more…

Vidhya Sagar SQL Server 2008, Troubleshoot .Net, SQL Installation, SQL Server 2008, Troubleshoot

Last week in our company we have started facing some error while uploading documents to the table. We have an database in which we will be uploading all the documents related to the customers, when the user tries to upload the document he \ she gets the error message as shown below

Read more…

Vidhya Sagar Troubleshoot Troubleshoot

Problem:

In our cluster environment I was testing SQL failover, when I failed over to passive node I can no longer launch SQL Server configuration manager (SSCM). When I tried to open SSCM, MMC has waited for 30 seconds and gave me the error below.

“Connection to target machine could not be made in a timely fashion”

Resolution:

Upon researching on this I found that WMI Service (Windows Management Instrumentation Service) is in hanged state. After restarting the service on passive node, it worked for me. Steps to restart the service is below.

• Go to Run –> type services.msc and press enter
• Right click on the service “Windows Management Instrumentation” and click on restart option in the menu
• Now launch SQL Server configuration manager, it should work fine now.

Vidhya Sagar Troubleshoot Administration

I’m starting this topic since last week I had faced a backup issue with compressed drive. In one of our server we have used compressed folder to take backup of our SQL databases. This is working fine and the db is used for OLTP application and it had grown about 73GB. Now we have started facing backup failures only for that database alone all other databases (less than 10GB) are running fine in the maintenance plan. I’ve checked the machine performance and SQL Server is the only process using 50% of CPU and 3GB of memory, other than that the server is not under stress and in fact that box is dedicated to SQL Server.

Read more…

Vidhya Sagar Troubleshoot Administration, Backup and Restore

In one of our server running Windows 2003 & SQL Server 2000 our system administrators has applied the service pack 1 and they have completed successfully. The next day night all the SQL jobs in another server (Windows 2000 & SQL Server 2000) which is configured to link the Win2k3 server has been failed with the error message below.

Executed as user: mydomain\sqlaccount. The operation could not be performed because the OLE DB provider ‘SQLOLEDB’ was unable to begin a distributed transaction. [SQLSTATE 42000] (Error 7391)   [SQLSTATE 01000] (Error 7312)  OLE DB error trace [OLE/DB Provider 'SQLOLEDB' ITransactionJoin::JoinTransaction returned 0x8004d00a]. [SQLSTATE 01000] (Error 7300).  The step failed.

Read more…

Vidhya Sagar Troubleshoot Administration, Linked Server