Solved

SBS 2003 migration to SBS 2001 and SBS 2003 SP1

Posted on 2011-09-29
5
414 Views
Last Modified: 2013-12-02
How critical is to upgrade it to SBS SP1 before doing the migration, most of our SBS 2003 were never updated to SBS SP1, just Windows Server SP2 and Exchange SP2
0
Comment
Question by:piotrmikula108
  • 3
  • 2
5 Comments
 
LVL 57

Accepted Solution

by:
Cliff Galiher earned 500 total points
ID: 36816431
It is important. You can install SBS Sp1over win2k3 sp2. They coexist, and order ove installation is not harmful. But, as always, have a safety net (aka backups.)

-Cliff
0
 
LVL 1

Author Comment

by:piotrmikula108
ID: 36817052
Hi Cliff

So these are the 5 components

- Windows Server 2003 SP1 - I have W2k3 SP2 so I can skip that?

- Exchange Server 2003 SP1 - I have SP2 so I can skip that?

- Windows SharePoint Services SP1 - I've got WSS 2.0 SP2, should I upgrade to WSS 3.0? I won't be migrating Sharepoint btw

- Windows Small Business Server 2003 Update KB891193 for Windows XP Service Pack 2 - seems like a very old update, do I still need it and the notes say "If you have already obtained Windows XP SP2, it is not necessary to download Windows XP SP2 for Client Deployment: all my XP PC have SP2 installed


- Windows Small Business Server 2003 SP1 - so this would be the only thing to install?

thank you
0
 
LVL 57

Expert Comment

by:Cliff Galiher
ID: 36893524
Do NOT upgrade to WSS 3. you are correct that you do not need to install kb891193.  So yes, SBS sp1 is all you need.

-Cliff
0
 
LVL 1

Author Comment

by:piotrmikula108
ID: 36970226
here is the error

I have enabled TCP/IP for that instance, firewall is diabled too
Server Error in '/' Application.
--------------------------------------------------------------------------------

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) 
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. 

Exception Details: System.Data.SqlClient.SqlException: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

Source Error: 

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.  

Stack Trace: 


[SqlException (0x80131904): A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)]
   System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +4849015
   System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) +194
   System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject) +4862333
   System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject) +90
   System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart) +342
   System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance) +221
   System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance) +189
   System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection) +185
   System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options) +31
   System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject) +433
   System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject) +66
   System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) +499
   System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +65
   System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +117
   System.Data.SqlClient.SqlConnection.Open() +122
   spencer.global.IsAdmin(String User) in C:\Inetpub\wwwroot\spencer\global.vb:24
   spencer.mainNav.ShowSubMenu(Int16 curTab, Int16 curSubTab) in C:\Inetpub\wwwroot\spencer\controls\mainNav.ascx.vb:60
   spencer.login.Page_Load(Object sender, EventArgs e) in C:\Inetpub\wwwroot\spencer\login.aspx.vb:34
   System.Web.UI.Control.OnLoad(EventArgs e) +99
   System.Web.UI.Control.LoadRecursive() +50
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +627

 


--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:2.0.50727.4927; ASP.NET Version:2.0.50727.4927

Open in new window

0
 
LVL 1

Author Closing Comment

by:piotrmikula108
ID: 37013090
I have installed the SBS SP1 but was forced to install the XP SP3 updated as well, but all worked well

thank you
0

Featured Post

Does Powershell have you tied up in knots?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

A safe way to clean winsxs folder from your windows server 2008 R2 editions
This article explains how to install and use the NTBackup utility that comes with Windows Server.
This tutorial will give a an overview on how to deploy remote agents in Backup Exec 2012 to new servers. Click on the Backup Exec button in the upper left corner. From here, are global settings for the application such as connecting to a remote Back…
This Micro Tutorial hows how you can integrate  Mac OSX to a Windows Active Directory Domain. Apple has made it easy to allow users to bind their macs to a windows domain with relative ease. The following video show how to bind OSX Mavericks to …

772 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question