MOSS MAN

MOSS Search not working on site level

noreply@blogger.com (Paul Zanbaka) — Wed, 25 Feb 2009 20:50:00 +0000

After adding another URL to access MOSS portal search stopped working completely.

you could access the portal through two URLs
A secure
https://portalname
and another url
http://portalname:7777

For some reason the https crawls were failing and I fixed that by editing contenet source to crawl this
http://portalname:7777 instead of https
This fixed s MOSS search on Portal level but did not work on top level sites.
After doing some research I was able to fix SharePoint search on site level by configuring Alternate Access Mappings and making this http://portalname:7777 instead the default

Why not create MCITP in SCCM or SharePoint 2007 (MOSS)?

noreply@blogger.com (Paul Zanbaka) — Thu, 06 Sep 2007 22:45:00 +0000

Microsoft new certifications MCITP allow IT pros to earn credentials equivalent to old school MCSE while focusing on a specific products.Why not create a specialization for SCCM or MOSS?Does anyone know if there are plans to do this in the near future?These products certainly require specialization…

Moving Sharepoint Portal Server 2003

noreply@blogger.com (Paul Zanbaka) — Thu, 06 Sep 2007 22:44:00 +0000

For example from a Two Server farm to Standalone; or from development to production.Install Sharepoint on the destination server but do not create a portal site instead chose to restore the site. Specify the content databases it is better to restore them on the machine first. This way you can chose any topology you like on the backup machine.
One Issue: I ran into one of my (100+) sites did not come up on back up portal.After troubleshooting for a while I found that the field (Id) in the Sites Table in _SITE db and the file (SiteId) in the Sites table in SPS_config did not match I changes the SiteId (SPS_conifg ) the site came up like a charm

I moved my blog to myITforum

noreply@blogger.com (Paul Zanbaka) — Tue, 04 Sep 2007 21:06:00 +0000

http://myitforum.com/cs2/blogs/pzanbaka/

What do you think of www.mycodekb.com?

noreply@blogger.com (Paul Zanbaka) — Thu, 30 Aug 2007 01:12:00 +0000

I created this site back in 2004 originally to search my code. I found myself looking for previous code snippets. I was storing these snippets in text files. Then the idea came to me what I can store my code and previous lessons learned online.
As I was building the site, what if others could store their code and we can search each others. I think I am on to something… What do you think?
Visit my site http://www.mycodekb.com/
Comment here or Vote on the left corner of this site

Content Database Migration from SharePoint 2003 to 2007

noreply@blogger.com (Paul Zanbaka) — Fri, 17 Aug 2007 18:51:00 +0000

This guide is aimed for a migrating a server farm with little customization.
I wrote it about two month ago as I was performing my migration. Enjoy...
1-Run Pre upgrade scan tool on WSS v2.0 or SPS 2003 farm
At the command prompt, perform one of the following actions, as appropriate for your situation:
If you are upgrading from SharePoint Portal Server 2003 to SharePoint Server 2007, type the following command at the command prompt
prescan.exe /c preupgradescanconfig.xml /all

If you are upgrading from Windows SharePoint Services 2.0 to Windows SharePoint Services 3.0, type the following command at the command prompt:
prescan.exe /all
Get any errors fixed in this stage before you move on.
You can check http://www.mycodekb.com/ for some of the errors I ran into and corrected.
Other useful slinks to troubleshoot your errors:
http://support.microsoft.com/kb/937291
Make sure you run this right before you perform the next steps.

2- Stand up and configure your new v 3.0 farm, Make sure all necessary services are started.

3-Create an IIS Website for each Web site in your in your v2 environment.
Increase ASP Script Timeout to 6000.modify the web.cofig file in the web application
Increase ASP।net execution Timeout
4- Copy all customization such as custom web parts and site definitions from your old farm to your all the WFE s on your new farm.

5- Set you WSS v 2 databses to Read Only.
Back up and restore, attach or copy the your content datasbes to the new server farm SQL Sever.
Before attaching datasbase in next step go and delete any triggers you may have created on the database, in my case I had created a trigger to limit versions on SPS 2003,, I really recommend cleaning here.
6-Attach the WSS v2 content database to your new Website using either SharePoint 3.0 Central Administration or
Stsadm tool see example below
stsadm -o deletecontentdb -url http://websitev3 -databaseserver DBSERVER-databasename WSS_Contentv3
stsadm -o addcontentdb -url http:// websitev3 -databaseserver DBSERVER -databasename CONTENTDBv2
This is going to take a while, go take a long break and hope for the best

Upgrade Migration Error: Halting upgrade... Microsoft.SharePoint.SPException: User cannot be found.

noreply@blogger.com (Paul Zanbaka) — Fri, 10 Aug 2007 14:05:00 +0000

This fixes 2 errors
Error 1) The migration upgrade error below[PortalSiteUpgradeAreaAndListingData] [12.0.1.0] [INFO]: Upgrade encountered an unexpected error.
Halting upgrade... Microsoft.SharePoint.SPException: User cannot be found. at Microsoft.SharePoint.SPUserCollection.GetByID(Int32 id) at Microsoft.SharePoint.SPSite.get_Owner() [SiteSequence] [ERROR]: User cannot be found.
Error 2) Manage Site Collection Owners User cannot be found

I've found a way to fix this but please try at your own risk and backup the database first! I think what is happening is that when SharePoint checks to see who the author (owner) of the site is, if the author doesn't exist Upgrade/migration fails.
The Owner of the site is stored in the Sites database table. The author of the site is stored in the Webs database table.

Step 1
Select * from Webs where FullUrl = ''
Here the full url is the one you are having problems with Copy the siteID it should look like this 3893DC55-756E-430C-8975-6214A531CAE1

Step 2
SELECT * FROM [FortBenn4_SITE].[dbo].[UserInfo] where tp_SiteId='3893DC59-756E-430C-8975-6214A531CAE1'
In here you get lots of records returned look for any valid user just copy the tp_ID for our example we make it 44

Step 3
The author and OwnerID bellow are the one you picked in step 2 (44) UPDATE [Sites] SET [OwnerID] = '44' WHERE [FullUrl]=’ '
Update Webs set Author='44' where FullUrl = ''
Step 4
Finally, go give ownership to the right user Go Windows SharePoint Services Manage Site Collection Owners Give the desired user ownership to the site
Let me know how it works make sure you test it on a backup environment

I kicked ... on the MCTS MOSS 70-630 Exam

noreply@blogger.com (Paul Zanbaka) — Fri, 10 Aug 2007 00:37:00 +0000

I took the MCTS Sharepoint exam yesterday, I thought it was too easy I scored 982. The bottom line most of the questions were short and more about the features of MOSS. Unlike typical Microsoft Exam which have long scenarios. If you are thinking about taking it ...just do it... I probably over studied.