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


Top 5 Contributors of the Month
david stephan
Post New Web Links

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

Posted By:      Posted Date: October 21, 2010    Points: 0   Category :SharePoint
 
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.


View Complete Post


More Related Resource Links

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?

Cannot install MOSS 2007 on Windows server 2003 SP2

  

Hi,

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

 

 


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.

 


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

Move SharePoint 2007 on Windows 2003 32-bit to Windows 2008 64-bit

  

I am planning to move SharePoint 2007 from a Windows 2003 32-bit system to a new Windows 2008 R2 64-bit server tomorrow afternoon.  I have done much research and found only one article that gives me enough information to go on for the migration.  Others in technet have cited this article; so, I expect it is the one go use.  However, before I begin, I wanted to see if anyone has anything else to add. 

Here's the article I'm planning to use:

http://www.combined-knowledge.com/Downloads/2007/How%20to%20move%20MOSS2007%20from%20W2003_32bit%20to%20W2008_64bit.pdf

Our current environment consist of one front end server (Windows 2003 32-bit running MOSS 2007) and one SQL server (Windows 2008 Standard 64-bit with SQL 2008 640bit).  So, we don't need to move the SQL databases - just the SharePoint front end.  We are moving to Windows 2008 R2 with MOSS 2007 (same SP and patch levels are planned).  

Our final goal is to move to SharePoint 2010 in the next week or two, but this seems to be the required first step.

Most of what I've read online contradicts other things.  I've found no consistency between articles.  

Thank you in advance for your assistance. 


Help to manage migration from farm WSS 2.0/MOSS 2003 to farm WSS 3.0/ MOSS 2007

  

Hello,

we need to move an application (only a site collection/portal site)  hosted in farm using  WSS 2.0(SharePoint Portal Server 2003 integrated with Project Server 2003) to a new farm where is installed WSS 3.0 and SharePoint Portal Server 2007.

We do not care at all about the part managed by Project Server 2003 . We are interested to obtain all lists, items and users information stored in the application (basically all the content part managed by MOSS 2003).

Which is the best strategy to get the job done ?

We have tried these steps to check if our strategy could work but it didn’t:

·

Upgrading Windows 2003 Server with .Net Framework 2.0 SP2

  

We have multiple websites deployed onto Windows 2003 WebServer running under .NET Framework 2.0 SP1 version and now we want to upgrade it to .NET Framework 2.0 SP2, so just wanted to check that after upgrading the .NET Framework on the server do we also need to re-deploy the websites by recompiling them in .NET Framwork 2.0 SP2 version or it's not necessary as they will automatically start referencing the latest assemblies?

Your early response will be much appreciated...

 


SharePoint 2007 Windows 2003 virtual machine on 64bit

  

On my old labtop (windows xp) I was using a SharePoint 2007 + Windows 2003 virtual machine (vhd)

(I was using the free Microsoft Virtual PC to use it) .But my labtop was very slow so I bought a new machine which has Windows 7 professional 64 bit.So how could I use my old vhd? I heard Virtual pc doesn't work on 64 bit windows.

After some search in google I read about VMWare Server which is free.I read v1 is better than v2.But I have no idea about it and didn't use it before is it safe?


I am too late but i will never give up

MOSS 2007 Services Not Starting After Adding 2008 R2 WFE to 2003 R2 Farm

  

In preperation for our 2010 upgrade we have been migrating our 2003 R2 infrastructure to 2008 R2. Our prior environment was server 2003 R2 DB server running SQL 2005 and one 2003 R2 WFE. We migrated the DB server to 2008 R2 and SQL 2008. The next step was to add a 2008 R2 WFE and then decommision the 2003 R2 WFE.

Setup was successful on the 2008 R2 box. However, in CA the services on the 2008 R2 WFE show "Starting". The CA service is the only service that shows "Started" on the 2008 R2 box. The Document Conversions Launcher Service, Document Conversions Load Balancer Service, Windows SharePoint Services Search and Windows SharePoint Services Web Application show "Starting". The Windows SharePoint Services Administration does not display a status.

What step am I missing to get all of the services running on the new 2008 R2 WFE so I can turn off the 2003 R2 WFE? I don't see anything in the error logs.

 


Windows Server 2003: Discover Improved System Info, New Kernel, Debugging, Security, and UI APIs

  

There's a lot to say about Windows Server 2003. First of all, it's the first operating system with built-in .NET Framework support, and it's the first 64-bit OS from Microsoft. But wait, there's more! There are lots of new features and APIs in this version as well. For instance, Windows Server 2003 features Hot Add Memory and a number of other arcane new tidbits. There are new APIs for handling threads, directories, and files, and new features like the low fragmentation heap for managing memory and system information. There's vectored exception handling and new UI APIs as well.OS internals expert Matt Pietrek takes a look at the additions he finds most interesting and useful so you'll have a good place to start when you dive into Windows Server 2003.

Matt Pietrek

MSDN Magazine June 2003


Security Briefs: Exploring S4U Kerberos Extensions in Windows Server 2003

  

Building Web sites that provide services external to the corporate firewall is tricky. Usually it's not desirable to grant corporate domain accounts to external clients, and from a purely practical standpoint Kerberos does not work well over the Internet due to the typical configuration of client-side firewalls.

Keith Brown

MSDN Magazine April 2003


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


Office 2003 integration with MOSS 2007

  

Hi

All my documents are opening as read-only when I open from SharePoint sites even when I click on "Edit in ..." option on some machines.

The users seem to have correct permissions on the site.

Regards,

Garima


Office 2003 integration with MOSS 2007

  

Hi ,

All my files/docs in MOSS 2007 open as read-only with Office 2003 standard edition in some machines.

The user seems to have sufficient permissions to edit but still not able to do so.

Any suggestion?

 

Regards,

Garima


Using MSDASQL on 64 bit windows 2003

  
Hi, I want to run the following SELECT * FROM OPENROWSET('MSDASQL', 'Driver={Microsoft Text Driver (*.txt; *.csv)}; DefaultDir=c:\test;','select * from ems.csv') I'm running SQL sever 2005 on windows server 2003 sp 2. I've run WindowsServer2003.WindowsXP-KB948459-v2-x64-ENU.exe from http://www.microsoft.com/downloads/details.aspx?FamilyID=000364db-5e8b-44a8-b9be-ca44d18b059b&displaylang=en I've not restarted the server. I can see MSDASQL under server objects->linked servers-> providers but when I run the query I get OLE DB provider "MSDASQL" for linked server "(null)" returned message "[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified". Msg 7303, Level 16, State 1, Line 1 Cannot initialize the data source object of OLE DB provider "MSDASQL" for linked server "(null)". I've read a lot of forum articles etc, but can't see what the problem is. Any advice would be appreciated    Sean

SQL express 2008 r2 on windows server 2003

  
install ends with the following error : "MsiEnumRelatedProducts failed to enumerate products with UpgradeCode='{1B117BA7-5BC1-419E-820E-7D4F3F412C7B}'. Error code: 1610."
Categories: 
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