MOSS 2007 Upgrade Quark

I have a MOSS 2007 Installation (SQL 2005) on a single box running Windows Server 2003. Since Windows 2003 is coming end of life I have to move this installation on a Windows 2008 R2 box
Please advice how should I proceed with seamless migration and if not possible via the SPSS Tools which 3rd party tool should I seek to make this happen.
Thanks a lot
SV

Hi Navdeep,
I will suggest you to use ULS log viewer OR check upgrade log to see the root cause of this failure. Below are couple of things which can be checked in addition.
1. Normally such error indicates that you are out of disk space. Check the disk space and try it again.
2. Sometimes it’s due to that there is a hard limit set in SQL on the PRIMARY file group for that particula database.
I hope it helps.
MachPanel - Premium Cloud Automation Solution

Similar Messages

Need to upgrade service providers of Moss 2007 to SharePoint 2013

I have upgraded the Moss 2007 Content database via native approach into SharePoint 2013. I am wondering how we can upgrade the service providers of Moss 2007 to SharePoint 2013 service applications.
Regards Restless Spirit

Hi Restless,
According to your description, my understanding is that you want to upgrade the service providers of MOSS 2007 to SharePoint 2013 service application.
Per my knowledge, you need to firstly upgrade the service providers of moss 2007 to SharePoint 2010 via database content, then upgrade SharePoint 2010 service applications to SharePoint 2013.
There are some useful articles for your reference:
MOSS 2007 upgrade - Shared-Services Provider SSP migration and my sites
MOSS SharePoint 2007 SSP migration to SharePoint 2010
Upgrade service applications to SharePoint 2013
Best Regards,
Wendy
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Wendy Li
TechNet Community Support

How to upgrade the extended web application for FBA from MOSS 2007 to SharePoint 2010?

Hi All,
Currently my farm version is MOSS 2007 with SP3.
I have a web application on port 80, and is based on windows authentication, and i extend it on the port 90, and the authentication is FBA with SqlServer.
I know that SharePoint 2010 has a new claims based authentication, and in a single web application you can do both windows authentication and FBA.
Now i want to know, when i migrate the MOSS 2007 port 80 and port 90, which method should i choose?
1. in SharePoint 2010 farm, Create a classic based web application on port 80, and extend it on port 90, enable FBA on port 90. It is the same as MOSS 2007.
2. in SharePoint 2010 farm, Create a claims based web application, and enable both windows authentication and FBA.
Thanks.

FBA requires claims so you'll need to create a claims based web application. Whilst you might extend the site to give you a FBA portal the web application itself will have to be claims based.
I would definitely be looking at using a database attach upgrade path in your case to give you the opportunity for testing as moving between authentication providers can be painful.

Which databases are required to be moved in MOSS 2007 for upgrade to 2010?

Hi,
We are planning to upgrade MOSS 2007 environment to SharePoint 2010. As a next step, I have to move the following databases. Please correct me if we need to also move the Shared Services (SSP) content databases.
Content Databases of Main website (move required)
Content Databases of SSP (move required)
Content Databases of Central Admin. (move not required)
Thanks in advance!
LM

Content Database, this is most important stuff.
if you have mysite and User profiles then you need to move the SSP to 2010. check the below blog for steps and understanding:
http://blogs.msdn.com/b/alimaz/archive/2009/11/08/upgrading-moss-2007-ssp-user-profiles-and-mysite-content-to-sharepoint-server-2010-using-db-attach-method.aspx
Yes you dont need the Central admin.
Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

Upgrade window 2003 to Window 2008 R2 approach (Moss 2007)

I have moss 2007 running window 2003 32 bit (1wfe and 1sql server). There quite a few customization that i dont know about. I need to move it to Window 2008 R2 or higher. Anyone have done this? I need a good approach with less risk and impact. I'll build
a new server in window 2008 R2 so it is not an in-place upgrade. I have Moss 2007 SP2, that will work on Window 2008 R2?

- make sure any/all customizations support 64-bit (for SP2007, this is especially true for iFilters, though occasionally WSP's as well)
- install 64-bit onto new server
- add to existing farm -Do you mean adding this using config wizzard?
- move all services from old server to new server - Do this in central admin? Can i just turn on on new server and leave it still on on the old server?
- redirect DNS
- disconnect old server from farm - Do you mean adding
this using config wizzard?
- disconnect old server from domain
- turn off old server
- celebrate

Window 2003 upgrade to window 2008 R2 for Moss 2007

I am currently running Moss 2007 on window 2003 32 bit. I need to move it to 2008 r2 64bit.
currently 1sql, 1webapp
i plan to add 64bit webapp(running window 2008 r2 64bit) to the farm, then remove the 32 bit webapp. here are my question
is that an ok approach since msdn recommend remove sql server first?
patch? does it have to be the same level? do i install 64 bit patches on win08 R2 or 32 bit? I am assuming 64 since i am running 64 bit window?
what about custom web part, fab40? do i need to redeploy?
Anyone have step by step instruction?

Refer to the following MSDN article
https://technet.microsoft.com/en-us/library/dd637753%28v=office.12%29.aspx?f=255&MSPPError=-2147217396
Also refer to the following article on best approaches to upgrade.
http://www.go4sharepoint.com/Forum/best-approach-upgrade-moss-2007-windows-22904.aspx
And yes, you need to migrate your custom web part and fab40 template manually by redeploying.
Cheers,

Upgrade MOSS 2007 to SharePoint 2010

Hi,
I am doing an upgrade from MOSS 2007 SP2 to SharePoint 2010 SP1 by database attach method. I have three content databases named :-
I) WSS_A - 1 GB
II) WSS_B - 22 GB contains 50 lists (On Production database size is 120 GB)
III) WSS_C - 1 GB
Machine used to Upgrade :- 2 core processor & 12 GB RAM
Database WSS_A and WSS_C has been upgraded successfully. But WSS_B failing again & again with SQL-Exeception in the logs and on screen exception is "Action 4.0.5.0 of Microsoft.SharePoint.Upgrade.SPContent ........ to Rollback"
In the preupgrade check all the three database reports are green. Please let me know how to solve the issue..
Navdeep Madan
http://navdeep19.wordpress.com

Hi Navdeep,
I will suggest you to use ULS log viewer OR check upgrade log to see the root cause of this failure. Below are couple of things which can be checked in addition.
1. Normally such error indicates that you are out of disk space. Check the disk space and try it again.
2. Sometimes it’s due to that there is a hard limit set in SQL on the PRIMARY file group for that particula database.
I hope it helps.
MachPanel - Premium Cloud Automation Solution

Upgrade the existing Moss 2007 licence to SharePoint 2013.

Our customer is using the Moss 2007 enterprise version with 500 CALs currently. They want to move to SharePoint 2013. I need to purpose the migration cost.
I am wondering -
does it possible to upgrade the existing Moss 2007 licence to SharePoint 2013.
Do customer has to purchase new licence?
Will existing licence help in any way if new licences are required?
Regards Restless Spirit

I assume you will have to purchase new licenses and you may get discount based on your company contract. Check below:
http://office.microsoft.com/en-in/sharepoint/sharepoint-licensing-overview-collaboration-software-FX103789438.aspx
http://blogs.technet.com/b/volume-licensing/archive/2013/08/08/licensing-how-to-sharepoint-server-2013-licensing-changes.aspx

For migration/upgradation of MOSS 2007 enterprise to Sharepoint 2013 System specification for new environment.

We have an installation of MOSS 2007 enterprise in production right now with sql server 2008 SP3 and Nintex workflow 7.
We need to migrate and upgrade to Sharepoint 2013. What system specifications we need to upgrade to sharepoint 2010 and sharepoint 2013.

A third party tool carries the advantages of being free of infrastructure requirements. If you don't have the budget for this, than you'll need to "double-hop" from SharePoint 2007 into SharePoint 2010 and then onto 2013.
The jump from 2007 to 2010 is likely to be the most painful. As John mentions any customisations and third party additions to your MOSS farm will need to be addressed as well.
Steven Andrews
SharePoint Business Analyst: LiveNation Entertainment
Blog: baron72.wordpress.com
Twitter: Follow @backpackerd00d
My Wiki Articles:
CodePlex Corner Series
Please remember to mark your question as "answered" if this solves (or helps) your problem.

Unable to enter MOSS 2007 License Key after SP2 upgrade - trial period about to expire

We are unable to enter the license key as stated in the title. The field does not allow any input. Central Admin shows that our trial period is about to expire very soon.
Our environment is MOSS 2007 (Office Sharepoint Server with Enterprise Client Access License) on Server 2003. SP2 is installed, the August 2011 CU (KB2553020) is installed, and the Microsoft suggested fix for this known problem is also installed (KB971620).
ie. Product expiration date is activated incorrectly. Since those fixes do not work, we are left with the manual entry of the license key. However, that also does not work.
Still, it shows that the trial period is about to expire. Apparently this fix is also included in any of the CU's after June 2009.
We have a valid license key for the Enterprise version and have the Enterprise client licenses as well. The License Synchronizer Job has succeeded.
I have searched the forum and have not seen a answer that resolves this issue.
Does anyone know what to try next ? We are running out of time.
Thanks in advance,
Peter
<></>
<> </>

Hi,
As far as I know, this issue occurs because the installation of the 2007 Microsoft Office SP2 activates the production expiration data incorrectly.
To resolve this issue, please install one of the following updates according to the following links:
Update for 2007 Microsoft Office servers (KB971620), 32-Bit Edition
Download the Update for 2007 Microsoft Office servers (KB971620), 32-Bit Edition package now. (http://download.microsoft.com/download/2/F/5/2F51AB71-1325-49D2-9CB9-18DEC4780E99/office2007-kb971620-fullfile-x86-glb.exe)
Update for 2007 Microsoft Office servers (KB971620), 64-Bit Edition
Download the Update for 2007 Microsoft Office servers (KB971620), 64-Bit Edition package now. (http://download.microsoft.com/download/5/B/B/5BBD34A9-C528-42B0-8A5F-9A8997B25C32/office2007-kb971620-fullfile-x64-glb.exe)
For more information about this issue, see
http://support.microsoft.com/kb/971620
After you install one of these updates, you do not have to redeploy the service pack. For information about how to deploy this update, please see the Microsoft TechNet article on how to deploy server updates:
http://technet.microsoft.com/en-us/library/cc263467.aspx
Thanks,
Rock Wang
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Rock Wang TechNet Community Support

MOSS 2007 Patch upgrade

Hello,
I need something urgent to know.
If SP3 was installed on Moss 2007 server, but never run product config wizard, then can we able to delete sp3 and reinstall it again? is it possible to remove sp3 if product config wizard was never run? What are the requirements to install sp3? Do i need
to also download cumulutive updates after installing sp3? do i need to install wss sp3 and moss sp3? how it works?
2. If the password for "moss_crawler" and "moss_service" (system accounts) are resetted, then where to apply the changes in SharePoint 2007? Where to update the passwords manually in SP2007?
Thanks
chirag

If SP3 is installed then i wouldn't recommed you to un-install as it might create inconsistencies and neither it makes sense unless you have a good reason to do the same. If PS config was never ran then you can do it though.
Requirements to install SP3 is that you need to have SP2 installed and updated and you don't need to install any CU after it unless you want to go even on higher version than SP3 i.e June CU 2013 which was the last patch for Moss and that ends the update
cycle for moss however there is one more security update post to that.
You will have to install MOSS and WSS 3.0 before running psconfig.
For moss_Crawler a/c you can update the password using below cmd or you can simply stop the Osearch service and while starting it you get the option to provide the default content access a/c
stsadm -o osearch -farmserviceaccount <domain\username> -farmservicepassword <
password>
You can take a look at this article for further assisntace in reference to changing search a.c password :- https://technet.microsoft.com/en-us/library/cc263313(v=office.12).aspx
For Farm a/c i.e the timer service a/c which i beleive is moss_service you have run below cmd:-
stsadm -o updatefarmcredentials -userlogin DomainName\UserName -password NewPassword
If this answer's your question then please mark it as answer so that it helps others.

How to install SharePoint MOSS 2007 PIK for Crystal Report Server XI R2?

My configuration is :
Moss 2007 without any Crystal Report or BO component. on one box with Windows 2003 server
Cyrstal Report Server XI R2 on another box
I have downloaded the kit installation: http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/webcontent/uuid/503988db-58c5-2b10-f79d-cb96700417f9 [original link is broken]
I used this one as they said:
BusinessObjects XI Release 2 SharePoint 2007 Portal Integration Kit
Download BusinessObjects XI Release 2 SharePoint 2007 Portal Integration Kit - ZIP 5MB
I do not have BO Enterprise.
Thanks,

Answered my own question. Managed to upgrade to 5.0 following this process, but follow these instructions with care...
1. Stop all CMS services in Config Manager.
2. Go to Add/Remove programs and click "change" for Crystal Reports Server XI. Click on "Modify" then change the entry for MySQL4.1.13a to "Entire Feature will be unavailable" (from Enterprise -> Server Components -> Servers - > Central Management Server). This will remove the existing mySQL version and any data/license key information/customisation, so be wary.
3. Install the desired version of mySQL.
4. Use the MySql command line to create a new database - "create DATABASE BOE115;"
5. In the Central Config Manager, select the CMS and display its properties. Select the Dependencies tab and remove the old version of mySQL and add the new version. Click on the Config tab, then Select Datasource. Select mySQL driver, then complete the details for the newly created database. Once complete it will still produce an error, at which point you need to select the options to Re-create the Current Datasource.
6. Once the datasource is sucessfully recreated, restart the Crystal service in the Config Manager.
7. Open the Config tool, and add your license key. Then Re-Enable all the servers within the Servers page.
8. Any other customisation or preferences would need to be re-applied.
This worked for me, but obviously take care as your existing mySQL database will be completely removed during the process.

Rich Text Editor for Content Editor WPs (MOSS 2007) disappears using Office 2013/Win7/IE 11

We've upgraded our computers to Win7/IE 11 but now when I try to edit our MOSS 2007 Content Editor Web Parts, the option to choose either the Rich Text Editor or Source Editor is gone, and all I get is a tiny HTML window. What do I need to do to get back
the Rich Text edit option?

Glad that it worked. One thing you need to be aware of Compatibility View is that it adds the entire domain to the View not just the URL. So if your website is
http://sample.mycompany.com it adds entire mycompany.com to the list.
This implies if you have another site in the same domain http://onemoresite.mycompany.com , then Compatibility View is applicable even for that site. This might cause issues if your other 'breaks' when
rendered in Compatibility Mode.

MOSS 2007 gives cross browser compatabity issue on firefox and chrome and also in higher version of IE (9 & 11)

I am getting browser compatablity issue when MOSS 2007 is used on IE 9 & 11 and on other browsers like firefox and chrome.
I also face issue while using the latest version of third party Intersoft WebUI 2014 R2 controls. Although the older version of Intersoft WebUI 2008 controls were working fine with MOSS in IE7 browser. But recently WebGrids are not loading
properly and the WebCombo dropdowns doesn't work. After apporaching the Intersoft on tis issue they said their latest version of Intersoft is compatible with MOSS 2007.
In this process of upgrade I learnt that the Intersoft Sample which comes with their setup can be run on Visual Studio 2010 and above. So I would like to know whether MOSS 2007 support VS 2010 or not.
Accepting response on my queries.

You've posted this in the wrong forum. 2007 questions should go into the SharePoint legacy forum.
This thread discussed 2007 browser support:
https://social.technet.microsoft.com/Forums/en-US/a3131e1f-b78b-46bd-bc46-750866b280bd/sharepoint-2007-ie-browser-compatability
Visual Studio 2010 will let you build tools for SharePoint 2007 however I'm not familiar with what you're trying to do or what intersoft webui does.

Copying/Duplicating MOSS 2007 Production environment to Test

Hi,
We are planning to upgrade our MOSS 2007 environment. For this, we need to create a test environment similar to the production. So far we have created the VMs (cloned) of the WFEs and created fresh SQL 2005 server. We have also taken
backup of all the content databases from the production SQL server and restored it on the test SQL server.
Please guide us on the next steps to configure the test environment to work.
Thanks,
LM

Hello LM,
Next step is attaching old content DB to web application. Now create a new web application and follow below link to use existing content DB with new web application:
http://it-diaries.blogspot.in/2010/01/how-to-change-web-applications-content.html
http://blog.qumsieh.ca/2009/02/13/attatching-a-content-db-to-a-web-application/
Hope it could help
Hemendra:Yesterday is just a memory,Tomorrow we may never see
Please remember to mark the replies as answers if they help and unmark them if they provide no help

MOSS 2007 Upgrade Quark

Similar Messages

Maybe you are looking for