Skip to main content

A problem I faced with WSS 3.0 configuration

I’d like to share a typical problem recently I faced with WSS 3.0 configuration on a Windows 2003 Server.

I created a virtual machine with Windows 2003 OS and named it “myvpc” in a hypothetical workgroup viz. “WKGP” (I initially planned to use it in stand-alone mode). Then I installed all available updates to the Windows Server and .Net framework 3.5 with IIS followed by Stand-alone installation of Latest WSS 3.0. The default team site and central administration site were working smooth. I even created another application using central administration.

Later I changed my mind and thought that it would be better if I include this virtual machine into our company’s local intranet Domain. At this point of time I had to change the PC name from “myvpc” to “SUDEV-VPC” due to some or other reasons.

Now, suddenly none of the SharePoint sites were accessible even from the “localhost“! I opened IIS console and noticed that “SharePoint Admin” site was stopped!!! I checked the systems log and found many errors stating “Cannot connect to SQL Server. MYVPC\Microsoft##SSEE not found“. I was surprised to see this, why SharePoint did not understand the change in name of computer.

I just thought lets run the “Configuration Wizard” again for the WSS. I did it but it failed too at the step-5 saying “Could not access search service configuration database“.

I uninstalled the WSS 3.0 completely and restarted the OS. I noticed that IIS don’t have the sites I created using WSS anymore.

I installed the WSS again, ran the configuration wizard but just to get a disappointment. The error continues to occur. This time I checked IIS and found that the sites I created with previous installation have been created again on the same port (sounds strange again, how new installation of SP came to know about it?)

The WSS 3.0 was using same database (Windows Internal Database aka SQL Server Embedded Edition). But at some location it was using previous computer name and at other it was using new name. (Surprised?)

So I thought lets re-install the Windows Internal Database itself. There is no direct way to uninstall it. So I uninstall the WSS 3.0 first. And then with help of MSDN link (http://technet.microsoft.com/en-us/library/cc708610.aspx) I uninstalled the Windows Internal Database as well. I removed the data files from “%windir%\SYSMSI\SSEE” as per their suggestion followed by a system restart.

Now I installed the WSS 3.0 in stand-alone mode, ran the configuration wizard and guess what? The configuration wizard ran successfully and I was able to access the default team site and admin site again.

It took quite some time to figure out this solution but it worked for me. In your case you may need to retain the backup of the content database and configuration database before un-install and install of WSS.

Labels:

Comments

Post a Comment

Popular posts from this blog

Comma separated list of values of single Database table field

Many times you need to create a comma seperated list of values in a table. Here is a line of T-SQL solution to get comma separated list of values of single field of a database table. DECLARE @commaSeparatedVal AS VARCHAR(MAX); SELECT @commaSeparatedVal = ISNULL(@commaSeparatedVal +',','') + CONVERT(VARCHAR,[SKU]) FROM PRODUCT PRINT @commaSeparatedVal
1 comment
Read more

Why SharePoint 2007?

It is rare for a technology product to attract as much attention as SharePoint has in recent years. The industry has historically paid little attention to new product suites, particularly those related to web design. SharePoint products and technologies, however, have managed to excite and rejuvenate industry followers, causing them to take notice of the ease of use, scalability, flexibility, and powerful document management capabilities within the product. A number of organizational needs have spurred the adoption of SharePoint technologies. Some of the most commonly mentioned requirements include the following: A need for better document management than the file system can offer —This includes document versioning, check-out and check-in features, adding metadata to documents, and better control of document access (by using groups and granular security). The high-level need is simply to make it easier for users to find the latest version of the document or documents they need to do th
1 comment
Read more

Creating Custom SharePoint Timer Jobs

In previous versions of SharePoint (or other platforms), if you had some task you wanted to perform on a scheduled basis, you'd have to either create a console EXE and schedule it to run via Windows Task Scheduler (ala AT.EXE) or create a Windows Service that went to sleep for a period of time. In order to install (and maintain) these tasks, you had to have console access to your production SharePoint (or other app) servers... something IT or admins wouldn't easily hand out. Addressing this issue, Microsoft has added something called timer jobs to Microsoft Office SharePoint Server (MOSS) 2007. Microsoft uses timer jobs to do things like dead web cleanup (purging unused sites from site collections) among others. To see what other timer jobs are out there, from Central Administration , click Operations and then Timer Job Definitions . Not only does Microsoft use timer jobs in MOSS, but you can create your own custom timer jobs to do your own scheduled tasks. What's nice a
Post a Comment
Read more