unable to connect to database or unable to connect the configuration database

Issue with SharePoint after installating the hotfix which solve DNS issue

If you install the DNS fix (KB 953230) and experience SharePoint trouble – such as error message which says unable to connect to database or unable to connect the configuration database.

You can follow the steps below if you're using Windows Internal Database/MSDE:
• Download and install SQL Management Studio Express (http://www.microsoft.com/downloads/details.aspx?FamilyId=C243A5AE-4BD1-4E3D-94B8-5A0F62BF7796&displaylang=en) if you don't have any SQL 2005 management tool available
• Connect the server using the following information
oServer: \\.\pipe\mssql$microsoft##ssee\sql\query
o Windows authentication
• Detach the SharePoint configuration database
• Reattach the SharePoint configuration database
• Restart your SharePoint server

Your issue should have been solved!!!

‘g_InstanceID’ is undefined

How to fix: Recurring Meeting Workspace error: ‘g_InstanceID’ is undefined
After changing the master page on a Meeting Workspace site, the recurring meeting workspace hyperlinks under “Select a date from the list below” do not work and throw a JavaScript error.

Please follow these steps to to overcome this error message "‘g_InstanceID’ is undefined "
1. At the top level of the site collection:- Browse to Site actions -> Site Settings -> Modify all site settings.
2.- Under the Galleries section, click 'Master pages and page layouts' to access the Master Page Gallery
3.Select 'Upload'. Browse to 12 hive\TEMPLATE\GLOBAL and select mwsdefault.master.
4.The 'Edit Item' page for the gallery will open. It's best to give this mwsdefault.master a new name in order to distinguish it from the original mwsdefault.master. Then click 'Check In'.
5.Publish the newly uploaded copy by selecting 'Publish a major version' from the item's dropdown box on the Master Page Gallery.
6.Approve the newly uploaded master page by selecting 'Approve/reject' from the item's dropdown box, selecting the Approved box, and clicking OK.

Back on the problem Meeting Workspace page:
-Select 'Site Actions' -> 'Site Settings' -> and then 'Master page' under the Look and Feel section
-Select the newly uploaded version of the mwsdefault.master in the Site Master Page and System Master Page dropdown boxes, and then click OK.
-the JavaScript controls on the Meeting Workspace will now work without producing the JavaScript error, making the other event dates browsable again.

I hope the above steps helps you to overcome this javascript error message and your meeting workspace template will work properly and never face this problem again. Thanks!!!

Cannot open file: it does not appear to be a valid archive. If you downloaded this file, try downloading the file again.

After you download a .ZIP file from a Microsoft Windows SharePoint Services document library, and then you try to open the .ZIP file, you may receive the following error message:
Cannot open file: it does not appear to be a valid archive. If you downloaded this file, try downloading the file again.

CAUSE
This problem may occur if HTTP compression is turned on in the Web Sites properties of Microsoft Internet Information Services (IIS) on the SharePoint virtual server. When you download a .ZIP file, IIS encodes the file as GZIP. However, the browser client passes the file directly to the unZIP program, without GZIP decoding the file. To determine if HTTP compression is turned on, follow these steps:
1. Click Start, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.
2. Expand the server (local computer) tree, where server (local computer) is the name of your IIS server.
3. Right-click Web Sites, and then click Properties.
4. Click the Service tab to view the HTTP compression properties.

Resolution:

change the MIME type for the .ZIP file from application/x-zip-compressed to application/octet-stream . To change the MIME type, follow these steps:

1. Click Start, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.
2. Right-click the server (local computer) tree, where server (local computer) is the name of your IIS server, and then click Properties.
3. Click MIME Types.
4. Scroll down the registered MIME type list to find the .zip entry.
5. Click the .zip application/x-zip-compressed entry, and then click Edit.
6. Change the MIME type value to application/octet-stream .
7. Stop and then restart the IIS Admin Service to apply the change to the MIME type.

The file that you selected could not be found

Few Days before, in our project, one of the user faced wierd error message which was never seen by my team. First of all lets focused the whole error message:
"The file that you selected could not be found. Check the spelling of the file name and verify that the location is correct."

When trying to open the sample dashboard in MOSS 2007 Enterprise Report Center site as an user with Read Only rights, we got this error message.
While troubleshooting, we compared two document libraries and reproduced the scenario.
After the excat replication of error message on a new document library,we found out the resolution which is quite simple.

Resolution:-
1. Go to your reports library where the workbooks are stored.
2. On the Settings menu, click Document Library Settings.
3. Under General Settings, click versioning settings.
4. Disable versioning.

I hope the above steps helps you to resolve your issue.
Thanks...

Usage Analysis Processing - Server Out of Memory error

In our company's project, We have Two enviornments Windows SharePoint Services and Microsoft office SharePoint Server 2007. Both are classified into 3 stages as Tes, QA and Production. In WSS 3.0 Test enviornment, when we tried to enable Usage Analysis processing, we got an error message :
"Server Out Of MemoryThere is no memory on the server to run your program. Please contact your administrator with this problem."

I can't find anything in the EVENT LOGS on the server that indicate an issue with this.
After doing lots of troubleshooting for more than 2 days, we found out the resolution.You can't believe it but the resolution is very simple and straightforward.

We found out that the application pool account was running under Network Service. We changed it to Domain admin account and after that did IISRESET.

Issue Resolved.
Cheers !

Note:-
The domain account should have the following rights as follows:-
1. It should be present in the WSS_WPG,WSS_ADMIN_WPG and IIS_WPG and Administrator group.
2.It should be present in the SQL SERVER Logins Section.
3. It should have DBCREATOR & SECURITY ADMIN Permissions in the SQL SERVER.

The application pool identity is essentially what the ASP .Net code of the site will be executing as. The user account used here must have the standard rights in order to run an application pool, and must obviously have rights to read and write to the SQL Server databases for the site.

Thanks...