.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
Gaurav Pal
Post New Web Links

MOSS 2007 to SharePoint Server 2010 Hybrid Upgrade Approach on Windows Server 2003 x64

Posted By:      Posted Date: September 13, 2010    Points: 0   Category :SharePoint
There's some guidance circulating about upgrading to 2010 with a mix of In-Place and Database Attach upgrade methods. My Central Admin and SharePoint Web App are on a 64 bit server, but it's running on Windows server 2003 x64 and not on Windows Server 2008 or 2008 R2. SharePoint Team Blog says Server 2008 or 2008 R2 is required for SP2010. If I want to do the hybrid upgrade approach, is it possible to first upgrade the OS to Server 2008 R2 on the server where my Central Admin and SP Web App runs?  Or will this break MOSS 2007?

View Complete Post

More Related Resource Links

Upgrade from MOSS 2007 Trial to Sharepoint Server 2010

I have a client who setup MOSS 2007 Trial and are coming up on the expiration.  Instead of buying a key for MOSS 2007 they purchased Sharepoint 2010.  I'm having some problems upgrading because its the trial.  What are my options for upgrading/migrating over to Sharepoitn 2010?

Upgrade from MOSS 2007 to SharePoint Server 2010 but with a catch...


... and the catch is that the MOSS 2007 Site Collection is contained in the SharePoint Central Administration v3 Web Application and therefore the SharePoint_AdminContent_... database which is used by Central Administration (not my doing btw).  Please let me know how to copy it to a new 2010 server farm and then upgrade just our sites and content while removing all of the 2007 Central Administration stuff.



Sharepoint 2003 + Windows Terminal Server 2008 + Office 2007 problem?

Hi, We have a customer where some users runs Windows Terminal Server 2008 with Office 2007. They open documents from a Sharepoint 2003 site. When they open an excel sheet they get a button in the document which says "Server workbook: Click edit workbook to edit this workbook" and there is a button: "edit workbook" The users clicks "edit workbook" but get an error message saying there is no connection to the server.  They are able to edit the document, but not save it back to the sharepoint site. Most other users work on their local computer with Office 2003. Here, everything works fine and there are no button/message stating its a server workbook.   Is this caused due to some compatability issues between Sharepoint 2003 and Office 2007?   Best regards, Thomas Hansen ErgoGroup AS

Install MOSS 2007 and ProClartity 6.3 (PAS6.3) on the same Microsoft Windows 2003 Server

An install of MOSS 2007 and ProClartity 6.3 (PAS6.3) on the same Microsoft Windows 2003 Server seems to be problematic. MOSS 2007 creates a default website and stops the normal default website. As soon as PAS 6.3 is installed it installs to this stopped default website. How can I overcome this issue?

Import Word docs with Metadata into SharePoint 2010 from Windows Server 2003


I need to import 700 Word docs (2003 & 2007) from Windows Server 2003 into a SharePoint Server 2010 library.  I only have a test server to work with right now and want to do as much pre-work before we launch the actual server. 

My goal: When we launch the shpt server, import all docs into a library so that columns propagate with metatdata automatically.

I'm not sure what the best approach is...

Can I can open each doc and add custom properties (maybe with InfoPath) to import as metadata, then import managed metadata through the term store tool and have it associate with the manually entered custom properties? I don't fully understand managed metadata, which might pose a problem.  And before I start importing terms, I thought I should find out if I've completely misunderstood how taxonomies work.

Or I have an excel spreadsheet with info about each doc in columns that can act as metadata. I could upload this as a list then associate each doc with the list.  But it seems wiser to enter the metadata into the documets.  

Is it possible to update my docs in advance so that uploading goes smoothly? I have help now for data entry that I won't have later.

I have no resources to spend on tools, and have to figure out and build this&nbs

Deployment of SharePoint Server 2010 on Windows 2003 Server Std Ed


After reviewing http://technet.microsoft.com/en-us/library/cc262485.aspx document on hardware/system requirements it appears that I will need to upgrade my Windows 2003 Server Std Ed to at least Windows 2003 Enterprise Ed in order for SharePoint Server 2010 Ent to be able to address more than the 4 GB (I believe) Windows 2003 Std only allows or addresses.  I have 32GB RAM on my Windows 2003 Std which also hosts the SQL Server 2005 Std Ed databases for other apps and will host SharePoint's database, as well--single platform install.  I also have two CPUs on this box which SQL (32 bit) uses.

So my question is:  can I easily upgrade Windows 2003 Std Ed to Enterprise without having to reinstall Windows 2003 and subsequently all other apps in Windows?
Kerry Jensen IT/Network Admin

Cannot install MOSS 2007 on Windows server 2003 SP2



I try to install moss 2007 on a developper workstation:

An error occured in the step 2 of the installation (installation of the administration database)

The error is as follow:


Exception: System.Data.SqlClient.SqlException: the procedure or function 'proc_SetDatabaseInformation' expected the '@Value' parameter, wich is not provided

i first try with an sql server 2005 database instance, then with an sql server 2008 database instance. Same problem.



In the log file, i can see this message before the exception:

Creating a new farm with config db SharePoint_Config content db SharePoint_AdminContent_59286dfd-6ead-46e6-8268-7b4c0f5025b1 server XXXXX for farm mode

The thing is, i do not want a farm mode installation, but the install wizard do not allow me to choose a non farm install.

Maybe this is non relevant, i don't know.


Thanks for your help



VS Studio WorkFlow Failed on Start in MOSS 2007 ON Windows Server 2008 64 Bit


I have created a sequential sharepoint workflow in WSP Builder in my Sharepoint Server and Deployed it.

But the workflows says Failed on start and retrying ans stops there forever says couldn't start the workflow.

I repaired .NET Framework 3.5sp1 installed

 tried this

 1. I tried again, in C Prompt:  Lodctr "c:\Windows\Microsoft.Net\Framework\v3.0\Windows Workflow Foundation\perfcounters.ini"  it says initiation file cannot be found

2   i again tried this C prompt Lodctr /R "c:\Windows\Microsoft.Net\Framework\v3.0\Windows Workflow Foundation\perfcounters.ini"

it says reloaded  from the system restored

i am still getting the same error.

When i manually go to my  C:\Windows\Microsoft.NET\Framework\v3.0\Windows Workflow Foundation i can see a folder for SQL that's it nothing more than that..

I dont know what is happening i am trying it from 2 days and still no solution.

any ideas would be real great help for me.

My system is 64 bit , Window server 2008, MOSS SP2, Visual Studio 2008 Version 9.0.30729.

.Net Framework 3.5 sp1

and WSP builder the one from Codeplex for 64 bit machines

Video: Coding a Long-Running Operation Page in SharePoint Server 2007 or Windows SharePoint Services

Watch this visual how-to video as you learn to write code to mimic the default long-running operations page (the "spinning wheel") in SharePoint Server 2007 or Windows SharePoint Services 3.0. (Length: 7:56)

Coding a Long-Running Operation Page in SharePoint Server 2007 or Windows SharePoint Services 3.0 (V

Watch the video and explore code as you learn how to write code to mimic the default long-running operations page (the "spinning wheel") in SharePoint Server 2007 or Windows SharePoint Services 3.0.

Best Practices for Content Types in SharePoint Server 2007 and Windows SharePoint Services 3.0

Learn best practices to develop, deploy, and manage custom content types, as well as scenarios for making updates to existing content types in lists.

HTTP Error 500.19 - Internal Server Error after SharePoint 2010 In-place upgrade

Hello We have done an SharePoint 2010 In-Place Upgrade. After the upgrade, we can access the Central Administration page without problems. However, when accessing the standard http port 80 site, the following error appears: Error Summary HTTP Error 500.19 - Internal Server Error The requested page cannot be accessed because the related configuration data for the page is invalid.   <fieldset><legend>Detailed Error Information</legend> Module IIS Web Core Notification Unknown Handler Not yet determined Error Code 0x80070032 Config Error The configuration section 'system.web.extensions' cannot be read because it is missing a section declaration Config File \\?\C:\inetpub\wwwroot\wss\VirtualDirectories\80\web.config Requested URL http://coolsharepoint:80/ Physical Path   Logon Method Not yet determined Logon User Not yet determined </fieldset> <fieldset><legend>Config Source</legend> 534: </location> 535: <system.web.extensions> 536: <scripting> </fieldset>

SharePoint 2010 Server: Cannot manage all user profiles from upgraded MOSS SSP database

I have upgraded an SSP database to SharePoint 2010 and successfully performed User Profile Synchronization with Active Directory, however I cannot manage ALL of the user profiles in the database. I go to "Manage User Profiles" in Central Administration and perform a filtered search (i.e. I want all DOMAIN accounts beginning with "j" so I search for "DOMAIN\j" in Manage User Profiles), but I don't receive ALL the user profiles back. I receive about 8 in return when I know there are about 20 starting with "j". If I create a new AD account beginning with "j" it is successfully synched with SharePoint 2010 and I see it in the Manage User Profiles. I ran an stsadm -o sync to clear any old synchronization information, and the Forefront Synchronization Service appeared to pull in many changes to existing accounts (including ones I can't currently manage), but I still cannot manage them using "Manage User Profiles". I really need to be able to manage all the profiles so I can manually edit some fields. Can anyone please help? Thanks in advance.

Do SharePoint 2007 and VS2010 have to be installed to the same Windows Server machine?

For WSS 3.0 development using VS 2005, I learned that we need to install VSeWSS to the Windows Server where the WSS 3.0 was installed.  For MOSS 2007 development using VS 2010, do we need to have VS 2010  nstalled to the same Windows Server?  Thanks, Jeffrey

MOSS 2007 upgrade to Sharepoint 2010 across domains

I recently did an upgrade at a customer site. I migrated their content successfully as well as their Mysites. Their MOSS farm was situated on a domain, let's say "domain 1". Due to a merger, their domain had to change to "Domain 2". The Sharepoint 2010  farm was set up on new domain. We now need to change the existing user logins from the upgraded content db to the new domain. domain1\user to Doamin2\user.  We considered a manual process, but it is simply not a viable option. Furthermore, the migrated mysites works fine, but the problem is, the users need to login with their old login details to view the content. Which is unacceptable. The mysite content now needs to be associated with the users on the new domain. Bear in mind that the users already have logins and permissions as per the previous configuration (domain1\user) I consideredd using the stsadm migrate user command, but that could also be laborious. The other concern is the SID associated to each login. I am not sure if the -ignoresidhistory switch will help, or if this command is even usable in SP 2010. I there possibly another, more effective method to accomplish these tasks, say a Powershell script or a magic wand?   Regards,   Warren  

Can WEBDAV be disabled in Sharepoint 2010 on a Windows Server 2008 R2?

Hello, we had some issues with WEBDAV use with Sharepoint 2010 placed behind WEBSeal proxies. We decided to only use FPSE (front page server extensions) for an external access to this portal. I cannot find a way, how to disable WEBDAV, or how to force clients to only use FPSE with this portal. It is fair, to say, that we would like to make such configuration on a server side, rather then configure client computers. We are running Sharepoint 2010 on a Windows Server 2008R2 server (i.e. IIS 7.5) thank you in advance for help/ideas Roman Cernovsky

Problem configuring SSRS 2008 with sharepoint 2007 on Windows server 2008

Hi All - I am unable to integrate SSRS 2008 with sharepoint 2007. I am new to this part please correct em if am wrong. I have 2 servers one for SQL and one for MOSS MOSS server. Windows server 2008 MOSS 2007 .Net 2008 with basic sql 2005 which comes default WSP builder Everything is working fine SQL server: Windows Server 2008 SQl server 2008 and configured SSRS BIDS. When I am trying to install SSRS plugin for MOSS it is not accepting on both the machines. Please help me if am missing something here. I configured sucessfully on one server but havent done on multi server environment. please help me.   Thanks Saritha    saritha k
ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend