MOSS MAN

Content Database would not attach to MOSS 2007

2010-08-06T11:53:00.005-04:00

Every time I attached Content Database to web application it deleted the stored procedures and failed with the following error in the log file:

[SPManager] [ERROR] : Cannot find the object "DatabaseInformation" because it does not exist or you do not have permissions.

I researched a lot of the posts out there and they were all dealing with upgrade uissues. The problem was this was not an upgrade this was the same database attached one day ago. After trying to to move a site off it and it failed so I tried to reattach it to get the site out the backup and it kept failing!

I tried using tools like DocAve and Metalogix to move data and/or site off it but they also failed.

Finally, I attached a clean db to the portal “New_DB”. Then I renamed the corrupted database to New DB.
It was now attached to the web application however it has 0 sites!
So I created a site on it called test
I then tracked down the ID for the corrupted site and the new test site from Corrupted Database Now “new_DB”
SELECT [Id]
,[SiteId]
,[FullUrl]
FROM [New_DB].[dbo].[Webs]

Once I the ids they look like this corrupted(887E0ED3-9CDD-42EC-8A38-6D397349169B)
new test site (0477CF53-F1C0-4CDD-9FDF-D1F61A10DE8A)
I went into the SharePoint_config db
WARNING: this is very dangerous make sure you backup the db and copy tables before altering.

I looked for the new test site I created
SELECT
*
FROM [SharePoint_Config].[dbo].[SiteMap]
where id ='0477CF53-F1C0-4CDD-9FDF-D1F61A10DE8A'
I grabbed the ApplicationId something like this '3B988D4F-4AD6-40F1-B7A8-8A4EBA9FC12D'

Now I ran an update statement to set the path and id for the new site (test) to the path and id of the corrupted site

update [SharePoint_Config].[dbo].[SiteMap]
set path= '/sites/oldsite'
where ApplicationId=
'3B988D4F-4AD6-40F1-B7A8-8A4EBA9FC12D'
and id='0477CF53-F1C0-4CDD-9FDF-D1F61A10DE8A'

update [SharePoint_Config].[dbo].[SiteMap]
set id= '887E0ED3-9CDD-42EC-8A38-6D397349169B’
where ApplicationId=
'3B988D4F-4AD6-40F1-B7A8-8A4EBA9FC12D'
and id='0477CF53-F1C0-4CDD-9FDF-D1F61A10DE8A'

And Voila just like that the site was up.
Now I was able to move the data I needed and everyone is happy:-)

Get ID for a SharePoint 2007 Database

2010-06-16T12:09:00.003-04:00

One easy way of figuring out the ID of your SharePoint 2007 db is to mouse over the content database in central Admin/ Application Management
Copy the shortcut for the link
Paste it and look at the string do not worry about the first two characters

Moving a Site to another content database in SharePoint 2007

2010-06-16T10:46:00.002-04:00

First you have to generate xml file that contains information about sites and content dbs.

Use this command

stsadm -o enumsites -url http://websername >C:\sites.xml

to create sites.xml

Clean it up and only leave site you want to move

Rename to move.xml to only have info about the site you want to move

Now run this command

stsadm -o mergecontentdbs -url http://websername /sites/sitename -sourcedatabasename Old_Content -destinationdatabasename New_Content operation 3 -filename C:\move.xml

Cannot Add Content DB to MOSS 2007 after SP2

2010-04-08T10:26:00.000-04:00

Cannot Add Content DB to MOSS 2007 after SP2
Through Central Administration:
you receive this error
Method not found: 'Microsoft.SharePoint.Administration.SPContentDatabase Microsoft.SharePoint.Administration.SPContentDatabaseCollection.Add(System.String, System.String, System.String, System.String, Int32, Int32, Int32, Boolean, Boolean)'.

Resolution:
Use stsadm to add content db
C:
cd C:\Program Files

cd Common Files

cd Microsoft Shared

cd web server extensions

cd 12

cd bin

stsadm -o addcontentdb -url http://BENNA0SHRPT2:7777 -clearchangelog -databaseserver Severname -databasename NewDBName

The evaluation version of Microsoft Office SharePoint Server 2007 for this server has expired

2009-12-15T10:42:00.000-05:00

We were getting this error when users were tryng to access their my sites and search!

i tried to resolve the error by doing what Joel Olson suggested here
http://blogs.msdn.com/joelo/archive/2008/01/02/evaluation-version-expired-but-not-really.aspx

However that did not work.

Finally our Sharepoint Admin Jessi marx found this article on Microsoft's site
http://support.microsoft.com/kb/971620

I reapplied the Product Key and everything worked Again!

Operation aborted (Exception from HRESULT: 0x80004004 (E_ABORT))

2009-12-15T10:14:00.001-05:00

You get this Error when you load some SharePoint 2007 Sites
Operation aborted (Exception from HRESULT: 0x80004004 (E_ABORT))

We were only getting this error on specific sites. We found that all these sites resided in the same content db.

After some investigation we found that some of the Stored Procedures in that db were missing.
We restored the latest version of the content db and everything worked fine!

Thank God for backups! LOL

Lost connection to site. Page will be reloaded, when the connection is restored...

MOSS Search not working on site level

2009-02-25T15:50:00.002-05:00

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)?

2007-09-06T18:45:00.000-04:00

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

2007-09-06T18:44:00.000-04:00

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

2007-09-04T17:06:00.000-04:00

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

What do you think of www.mycodekb.com?

2007-08-29T21:12:00.000-04:00

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

2007-08-17T14:51:00.000-04:00

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.

2007-08-10T10:05:00.000-04:00

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

2007-08-09T20:37:00.000-04:00

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.

"Auto F5 reload window" options
Default timeout	*
Timeout for this page	*
Add random value to timeout between 0 and	*
Show and hide menu
Ignore everything after these symbols in URL(separate with spaces)
Include the separators in the URL saved
Hide menu when clicking outside the menu
Prolong timeout on mouseclicks or keyboard input
Reload all pages with default timeout, which has no timeout set
*Format examples: hh:mm:ss, h:m:ss, m:sss, s etc. like 1:20:30 oder 500 oder 3:100

"Auto F5 reload window" options
Default timeout	*
Timeout for this page	*
Add random value to timeout between 0 and	*
Show and hide menu
Ignore everything after these symbols in URL(separate with spaces)
Include the separators in the URL saved
Hide menu when clicking outside the menu
Prolong timeout on mouseclicks or keyboard input
Reload all pages with default timeout, which has no timeout set
*Format examples: hh:mm:ss, h:m:ss, m:sss, s etc. like 1:20:30 oder 500 oder 3:100

"Auto F5 reload window" options
Default timeout	*
Timeout for this page	*
Add random value to timeout between 0 and	*
Show and hide menu
Ignore everything after these symbols in URL(separate with spaces)
Include the separators in the URL saved
Hide menu when clicking outside the menu
Prolong timeout on mouseclicks or keyboard input
Reload all pages with default timeout, which has no timeout set
*Format examples: hh:mm:ss, h:m:ss, m:sss, s etc. like 1:20:30 oder 500 oder 3:100

"Auto F5 reload window" options
Default timeout	*
Timeout for this page	*
Add random value to timeout between 0 and	*
Show and hide menu
Ignore everything after these symbols in URL(separate with spaces)
Include the separators in the URL saved
Hide menu when clicking outside the menu
Prolong timeout on mouseclicks or keyboard input
Reload all pages with default timeout, which has no timeout set
*Format examples: hh:mm:ss, h:m:ss, m:sss, s etc. like 1:20:30 oder 500 oder 3:100