Microsoft SQL Server Management Studio Express (SSMSE) 2005 Installation Error

Today I had to download the SSMSE 2005 from the Microsoft downloads site and when I was installing on a fresh new sever it was complaining about a DLL.

Then I had a copy of a previously downloaded MSI and when I did the installation it went through without any issues.

I was curious to see the file sizes and actually there was a difference.

Please let me know if any one else had a similar kind of experience.

TRIM Any Word Seach Error (GetRecordset64) Workgroup Error Timeout expired

Our TRIM production server is running on a Windows 2003 R2 server with all the patches and SQL Server 2005 SP2.

We have recently started receiving an error when we do an “Any Word” search for words such as "personal care". These are not noise word.

Here is the error message.



Based on my initial investigation it seems like this message is generated from the database server and being relayed to the user by the TRIM workgroup server.

We contacted the HP TRIM helpdesk and they mentioned this error generally appears when the MDAC is corrupted.

Their recommendations were to:

1. Reregister the OLE32.DLL
2. Repair MDAC - you can get the latest version for www.microsoft.com
3. Reinstall MDAC
4. Reinstall TRIM
5. Reinstall the Operating System
6. Reimage the computer

When I mentioned the time constraints, they recommended trying a Wild Card search. Example: personal* care

Wow, actually that worked and I thought it will be useful to share this tip.

At this stage I’m not exactly sure how it fixes the issue, but I’m assuming the SQL query passed to the database might be the difference. I’m planning to run SQL Profiler to see the difference. I’ll share my experience when it is completed.

Turn off SharePoint (MOSS) 2007 Custom Error Messages

I always forget these steps, so thought of adding a reference to this great post from Steve Pietrek.

1. Navigate to the site directory.
2. Backup web.config.
3. Open web.config.
4. Switch Custom Errors off. Search for “customErrors” and set the value to “Off” instead of “On”. You can also set the value to “RemoteOnly” to troubleshoot a production issue.
5. Enable CallStack. Search for “CallStack” and set the value to “true” instead of “false”.
6. Save web.config.

http://stevepietrek.com/2007/07/28/turn-off-sharepoint-custom-error-messages/

Remote Name Could not be Resolved in SQL Server Reporting Services

I recently had to change the machine name of my development server. It broke my Reporting Services connection via SQL Server Management Studio (SSMS). I updated the Reporting Services Configuration setting but SSMS was complaining saying “Remote Name Could not be Resolved”.

This was finally fixed by updating new machine name setting on the following file C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer\rsreportserver.config

http://[machinename]/reportserver