Tech-Motive

MOSS 2007 setup program may crash on 64 bit Windows 2003. You can get the following error message: Setup did not complete successfully. We are sorry for the inconvenience. If it is happening with you then just check one thing: Open Terminal Services Configuration. Click Server Settings. Right-click Permission Compatibility, and then click Properties. Select the Full Security check box, and then click OK. Now you should be able to install MOSS 2007. Please note that directly changing the Terminal Services Configuration settings can be dengerous. So, be very careful before changing.

In 64 bit Windows 2003, you may need to change the emulation mode of IIS depending upon the cases and conditions. To change the IIS emulation mode to 32 bit to 64 bit and vice versa, do the followings: Open command promp and run the following command cd C:\Inetpub\Adminscripts (I am assuming that C is your windows drive) cscript adsutil.vbs set w3svc/AppPools/Enable32bitAppOnWin64 1 (to make it 32 bit) cscript adsutil.vbs set w3svc/AppPools/Enable32bitAppOnWin64 0 (to make it 64 bit) iisreset

I recieved the following error which I never experienced before in our Sharepoint portal which has SSRS configured in MOSS integrated mode: The resource object with classname "ReportServer" and key "SharedDataSource" was not found. After searching for a while, I found that the ReportServer.resx file was not there inside the App_GlobalResources folder in the virtual directory of the respective portal. I just copied the ReportServer.resx from App_GlobalResources folder under wwwroot and finally pasted it inside the portal's virtual directory. Problem suddenly vanished.

For a fresh MOSS Administrator like me, it's very important to know the maximum capacity of sharepoint objects like lists, libraries, pages, sites, users etc and to get the optimum performance benefit upto these limits. Limits that are used over here are can be used to design a portal or a farm to get the best out of MOSS 2007 and crossing this limit may cause MOSS 2007 to create performance bottlenecks: Site collections (Database scope) : 50000 Web sites (Web site scope)  : 2000 Web sites (Site collection) : 250000 (Nested Subsites) Documents (Folder scope) : 2000 Documents (Library scope) : 2 million (Nested Folders) Users ( Web site scope) : 2 million Items (List scope) : 2000 Web Parts (Page scope)  : 100 Web Part personalization (Page scope) : 10000 Document size (File scope) : 50 MB  (2 GB if WSS SP1 is applied) Checkout this link:  http://blogs.msdn.com/bgeoffro/archive/2008/03/19/list-atta...

Recently I had a requirement to delete a user's mysite as the user had left the organisation. The simplest way I found was to directly go to the sharepoint mysite by using the following url: http://(mysite_url)/personal/(user_name)/_layouts/settings.aspx The username should not include the domain id. Clicked on "Delete this site" option in the highlighted oval and the job was done.