.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

Migrating MOSS 2007 from 32-bit Windows OS to 64-bit Windows OS

Posted By:      Posted Date: October 12, 2010    Points: 0   Category :SharePoint


We currently have a MOSS 2007 installation which is running several application templates, services (i.e. indexing), and a custom workflow solution which involves assemblies compiled from Visual Studio 2005 Professional, Sharepoint Designer 2007, InfoPath Forms 2007 and a SQL Server 2005 Enterprise Edition database for the Sharepoint content database and so forth. I have a feeling I know the answer to this question, but because we are having so many problems with getting Windows Server 2003 Enterprise Edition (we currently have Standard), I was trying to find an alternative. The main reason we need to upgrade from Standard to Enterprise is because we need to migrate our Sharepoint databases to this new server, but with Standard, we have a limit of 4G RAM, and we have 32G RAM ready to install, but again, we cannot because of the 4G RAM limitation with Windows Server 2003 Standard. I know there will probably be an issue with migration from the 32-bit version of SQL Server 2005, not to mention known issues with the indexing service in Sharepoint. But, I thought I might run it by the experts in this forum to see if perhaps there is a workaround I am unaware of, or something i am overlooking. Any help, suggestion or point in the right direction would be greatly appreciated.



View Complete Post

More Related Resource Links

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

WebPart Deployment in windows 2008 R2 with Moss 2007

Hello, I have build one employee directory webpart that gets necessary information of user from sharepoint site. i have deployed in my testing server "Windows Server 2003 and Moss2007" and it's work fine. When i tried to deploy on my production server "Windows Server 2008 R2 with Moss2007". It give me security error. Request for the permission of type 'Microsoft.SharePoint.Security.SharePointPermission, Microsoft.SharePoint.Security, Version=, Culture=neutral, PublicKeyToken=71e9bce111e9429c' failed." I have also created security policy file and added reference to web.config. Still i getting same error please help on this. i am stuck here and not able to find any way to get out of this.

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?

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

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?

can we install MOSS 2007/2010 on windows 7 ultimate (x64)???

Can we install both moss 2007  and moss 2010 on windows 7 ultimate(x64) ? if yes, please let me know the procedure. I am a beginner and hence i would try the trial version provided by microsoft.

How to integrate windows authentication with FBA in MOSS 2007

I have a scenario in wchich my domain users are login in moss sites through windows authentication in intranet zone. They want to use the site through internet also through FBA. Only thing is that they want to use the sane user Id and password(windows authentication ID) through FBA also. So how to store windows authentication information in FBA database. Also i dont need to give the accesss separately. The access should automatically get captured as provided in intranet zone.

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



Upgrading servers in a MOSS 2007 farm from Windows 2003 SP2 to Windows 2003 R2

Are they any particular pitfalls to watch out for here?  We have two front ends in a load balance with an index server, andtwo SQL servers forming a failover cluster.

MOSS 2007:Specified program requires a newer version of Windows


Hello All

I have override the onSaveChange event. In this event i have create some custom columns in SharePoint custom list and then added a event handler for item adding event. But it will create the columns but i gives me an error

Specified program requires a newer version of Windows

Please suggest any workarroud. It already takes my whole day

upgrade from windows 2003 to windows 2008 R2 for moss 2007 sp2


We are having MOSS 2007 SP2 on my windows server 2003 OS and now we r plainng to upgrade windows server 2003 to windows server 2008 R2. Could anyone let me know what are the steps i need to do before i upgrade and how to do the upgrade any precautions i need to take, any potential problems i may face..some thing like that.

Thanks in Advance.


Windows Azure: Tips for Migrating Your Applications to the Cloud


Windows Azure is already helping many companies move their apps into the cloud. We'll share some of the tips and tricks that we discovered working with customers on real-world migrations.

George Huey, Wade Wegner

MSDN Magazine August 2010

Shelley Powers: Migrating Your ASP Apps from Windows NT 4.0 to Windows 2000


In order to take advantage of new features in Windows 2000 and IIS 5.0, you must first migrate your Windows NT 4.0-based ASP applications to Windows 2000. This article provides a multi-step migration plan. It discusses how to install and configure IIS 5.0, set up security, migrate MTS packages to COM+ applications, and handle differences in the ASP object models. Also included are guidelines for setting up Visual Basic and Visual C++ for development in Windows 2000 and information on what to expect when moving ASP components to the new OS.

Shelley Powers

MSDN Magazine August 2000

How can Install Office 2007 on Windows server 2008 R2 64 bit machine in WSS 3.0

I have  64 bit machine  and Windows server 2008 R2 has installed. i have successfully install WSS 3.0  , but  when i tried to install  office 2007 ,  one  error  has  come  "OS is not compatible "  i thought  it was asking  for 64 bit office  2007   and i go through the  google and R&d find no 64 bit office is available ,  i have used   excel .dll in my custom code  so my problem is that   how can  install office 2007  on 64 bot OS 2008 r2  machine .  if anyone can help   me  , please let me know . thanks in advance

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.

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