• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1111
  • Last Modified:

Best practice to reinstall SQL 2000 after SQL 2005 on SBS 2003 R2 ?

OS:
MS SBS 2003 R2

Additiional Server Apps:
Microsoft Sharepoint (using SQL 2005)
Microsoft CRM (using SQL 2005)
Microsoft Dynamics GP Accounting (using SQL 2005)

Hello,

Recently (before I came aboard) the company's accountant uninstalled SQL 2000 in an effort to upgrade to SQL 2005 to run both MS CRM and MS Dymanics.

This of course broke WSUS, SBSMonitoring and Sharepoint. I upgraded the sharepoint instance to SQL 2005 without any problems.

I would like to get WSUS and SBSMonitoring repaired.

After a bit of research, I found that MS does not support upgrading SBSMonitoring or WSUS to SQL 2005.

Should I re-install SQL 2000 (along side SQL 2005) and if so, what is the best way to do it?
Would it be better to upgrade SBSMonitoring or WSUS to SQL 2005?

My constraints are:
Not loosing the CRM, GP Dymanics and Sharepoint SQL 2005 databases.
I do not have a second box to test with.

Any suggestions would be greatly appreciated.

Thanks in advance.
0
PortableLighting
Asked:
PortableLighting
  • 10
  • 8
1 Solution
 
SQL_SERVER_DBACommented:
My constraints are:
Not loosing the CRM, GP Dymanics and Sharepoint SQL 2005 databases.
I do not have a second box to test with.


I've don inplace upgrades with All 3, no problems...
0
 
PortableLightingAuthor Commented:
So you suggest just running SBSMonitoring and WSUS off of SQL 2005?

Do you know why Microsoft does not recomend  using SQL 2005 for SBSMon and WSUS with SQL 2005?
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
NO!  Not only can you not upgrade SBSMonitoring to SQL 2005, you can't even run it on SQL 2000.  It can only run on MSDE.

To repair monitoring, you need to reinstall it following these steps:

1. Control Panel -> Add Remove Program -> Windows Small Business Server 2003.
   Set Server Tools to Maintenance. Set Monitoring to Uninstall and continue the setup process.
2. Control Panel -> Add Remove Program -> Microsoft SQL Server Desktop Engine (SBSMonitoring) -> Remove.
3. Rename the C:\program files\Microsoft SQL Server\MSSQL$SBSMONITORING Folder.
4. Reboot the server.
5. Control Panel -> Add Remove Program -> Windows Small Business Server 2003.
   Set Server Tools to Maintenance. Set Monitoring to Install and continue the setup process.
6. Reboot the server.
7. Start MSSQL$SBSMONITORING and SQLAgent$SBSMONITORING services.
8. In Server Management Console -> Monitoring and Reporting: run the "Set Up Monitoring Reports and Alerts wizard

As for WSUS... please review the WSUS on SBS guidelines which explain how do that as well:  http://sbsurl.com/wsus

Jeff
TechSoEasy
0
 [eBook] Windows Nano Server

Download this FREE eBook and learn all you need to get started with Windows Nano Server, including deployment options, remote management
and troubleshooting tips and tricks

 
PortableLightingAuthor Commented:
Thanks TechSoEasy,

I am not very SQL savvy, but have a decent handle on most other aspects.
I don't really understand the differnce between the MSDE and SQL server. I thought the original instance of SBSMonitoring was running on the SQL 2000 engine, so I figured it got broken when SQL 2000 was uninstalled. Looking at my services I see that the MSSQL@SBSMONITORING service is running, but the SQLAgent$SBSMontiroing service won't start.

After trying to start the SQLAgent$SBSMonitoring service manually, the event log reports Event ID: 103, "SQLServerAgent could not be started (reason: Unable to connect to server 'XXSERVERNAMEXX\SBSMONITORING'; SQLServerAgent cannot start)."

I don not see any service refering to WSUS, so looks as if it is not even installed.

I will try your described fix later when I can take the server down (for the reboots) and in the mean time I will look at the WSUS document you pointed me to.

Also it looks like the Dell PowerEdge System Mangement tools wants to run on SQL, is their a good practice for installing that as well? (I could post that as a sperate question if you would like.)

Thank you for your time and knowledge!
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
If the SQLAgent$SBSMonitoring service won't start, because it can't connect, you'll need to reinstall Monitoring as described.  However, one thing I failed to mention is that you need to reapply SBS SP1 after reinstalling Monitoring because that's how the MSDE instance gets updated to SP4 which would be required.

This is assuming that the server was properly updated to SP1 prior to now.

You can download SBS SP1 directly from:
http://download.microsoft.com/download/0/5/0/0503C927-F573-43A1-A184-97D755345F59/SBS2003-KB885918-SP1-X86-ENU.EXE

Jeff
TechSoEasy
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
"I don not see any service refering to WSUS, so looks as if it is not even installed."

Double check by looking in the MSSQL\Data folders in Program Files to make sure there isn't a WSUS database file.

As for the Dell System Managment, reinstalling that would recreate it's MSDE instance as well.

Jeff
TechSoEasy
0
 
PortableLightingAuthor Commented:
Thanks ThechSoEasy,

I already reinstalled the SBSMontioring (as you described) and everything seems to be working well with it. Yes it was already upgraded to SP1, but I will re-apply the patch as you suggested.

I still have to install the WSUS and I will also install the Dell System Managment tools.

Thank you very much for your feedback.
-Chris
0
 
PortableLightingAuthor Commented:
I just checked and right now it is SBS 2003 SP2.

Do I still need to re-apply SP1?

Thanks,
-Chris
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
You need to understand that what may show in a SYSTEMINFO or other version display is the Service Pack of Windows Server 2003, not SBS itself.  There is no SBS SP2 currently so what you're seeing is Windows Server 2003 SP2.

The link I provided above is SBS SP1 as described here:
http://download.microsoft.com/download/e/0/f/e0fee8ce-768d-41c0-8871-9bc48e0b3fc3/ToDownLoadFilesandReadInstructions.htm

Jeff
TechSoEasy
0
 
PortableLightingAuthor Commented:
Ok, honestly I am not an idiot when it comes to servers, just SQL and SBS.
This is my 1st time having to deal with both SQL and SBS.

So MS has put out a SP for SBS 2003 that is saperate from 2003 Server SPs?

I have no idea if SBS SP1 has been installed. Looking at the updates in Add/Remove, I cannot find anything refering to SBS 2003 SP1.

I am weary aobut applying the SP because we have had SPs break some of our functionality.

Does it make a diference that this is SBS 2003 R2 Premium Edition?
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
"So MS has put out a SP for SBS 2003 that is saperate from 2003 Server SPs?"

Yes.  In order to install SBS SP1 you had to install 4 other updates, one of which is Server 2003 SP1.

"I have no idea if SBS SP1 has been installed"

Please run SYSTEMINFO at a command prompt and post the results here and I will explain how to look for this.

"I am weary aobut applying the SP because we have had SPs break some of our functionality."

Service Packs can indeed break functionality... but not applying them will cause your systems to fall out of Microsoft's standard support cycle.  It's always important to review all the release notes for applying any Service Pack.  In this instance, though, I had recommended RE-applying SBS SP1, meaning I was assuming that SBS SP1 had already been installed.  Please note above my comment which states, "This is assuming that the server was properly updated to SP1 prior to now."

"Does it make a diference that this is SBS 2003 R2 Premium Edition?"

It could make a difference... but it would depend on whether the server was upgraded to R2 or the original installation media was R2 to begin with.  If it was upgraded, then you'd reapply the SP.

Jeff
TechSoEasy
0
 
PortableLightingAuthor Commented:
Thanks again for your insight.

The orignial media and the orginal install is SBS 2003 R2 Premium Edition.

Here is the SYSTEMINFO output:

Host Name:                 XSERVERX
OS Name:                   Microsoft(R) Windows(R) Server 2003 for Small Busines
s Server
OS Version:                5.2.3790 Service Pack 2 Build 3790
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Primary Domain Controller
OS Build Type:             Multiprocessor Free
Registered Owner:          XXXXXXXXX
Registered Organization:   XXXXXXXXX
Product ID:                74995-066-9160156-42371
Original Install Date:     6/20/2007, 6:01:35 PM
System Up Time:            0 Days, 19 Hours, 38 Minutes, 35 Seconds
System Manufacturer:       Dell Inc.
System Model:              PowerEdge 2900
System Type:               X86-based PC
Processor(s):              4 Processor(s) Installed.
                           [01]: x86 Family 6 Model 15 Stepping 7 GenuineIntel ~
1862 Mhz
                           [02]: x86 Family 6 Model 15 Stepping 7 GenuineIntel ~
1862 Mhz
                           [03]: x86 Family 6 Model 15 Stepping 7 GenuineIntel ~
1862 Mhz
                           [04]: x86 Family 6 Model 15 Stepping 7 GenuineIntel ~
1862 Mhz
BIOS Version:              DELL   - 1
Windows Directory:         C:\WINDOWS
System Directory:          C:\WINDOWS\system32
Boot Device:               \Device\HarddiskVolume2
System Locale:             en-us;English (United States)
Input Locale:              en-us;English (United States)
Time Zone:                 (GMT-05:00) Eastern Time (US & Canada)
Total Physical Memory:     4,095 MB
Available Physical Memory: 1,716 MB
Page File: Max Size:       10,066 MB
Page File: Available:      7,713 MB
Page File: In Use:         2,353 MB
Page File Location(s):     c:\pagefile.sys
Domain:                    XDOMAINX.local
Logon Server:              \\XSERVERX
Hotfix(s):                 64 Hotfix(s) Installed.
                           [01]: File 1
                           [02]: File 1
                           [03]: File 1
                           [04]: File 1
                           [05]: File 1
                           [06]: File 1
                           [07]: File 1
                           [08]: File 1
                           [09]: File 1
                           [10]: File 1
                           [11]: File 1
                           [12]: File 1
                           [13]: File 1
                           [14]: File 1
                           [15]: File 1
                           [16]: File 1
                           [17]: File 1
                           [18]: File 1
                           [19]: File 1
                           [20]: File 1
                           [21]: File 1
                           [22]: File 1
                           [23]: File 1
                           [24]: File 1
                           [25]: Q147222
                           [26]: KB933854 - QFE
                           [27]: SP1 - SP
                           [28]: KB888619 - Update
                           [29]: KB912442 - Update
                           [30]: KB916803 - Update
                           [31]: KB931832 - Update
                           [32]: KB931978 - Update
                           [33]: KB928365 - Update
                           [34]: Q927978
                           [35]: Q936181
                           [36]: IDNMitigationAPIs - Update
                           [37]: NLSDownlevelMapping - Update
                           [38]: KB925398_WMP64
                           [39]: KB933566-IE7 - Update
                           [40]: KB937143-IE7 - Update
                           [41]: KB938127-IE7 - Update
                           [42]: KB914961 - Service Pack
                           [43]: KB921503 - Update
                           [44]: KB924667-v2 - Update
                           [45]: KB925876 - Update
                           [46]: KB925902 - Update
                           [47]: KB926122 - Update
                           [48]: KB927891 - Update
                           [49]: KB929123 - Update
                           [50]: KB930178 - Update
                           [51]: KB931784 - Update
                           [52]: KB931836 - Update
                           [53]: KB932168 - Update
                           [54]: KB933360 - Update
                           [55]: KB933566 - Update
                           [56]: KB933854 - Update
                           [57]: KB935839 - Update
                           [58]: KB935840 - Update
                           [59]: KB935966 - Update
                           [60]: KB936021 - Update
                           [61]: KB936357 - Update
                           [62]: KB936594 - Update
                           [63]: KB936782 - Update
                           [64]: XpsEPSC
Network Card(s):           1 NIC(s) Installed.
                           [01]: Broadcom BCM5708C NetXtreme II GigE (NDIS VBD C
lient)
                                 Connection Name: Server Local Area Connection
                                 DHCP Enabled:    No
                                 IP address(es)
                                 [01]: 192.168.XX.XX

Thanks again for your time and help,

-Chris
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Okay... so you won't have to install SBS SP1 again, but you still may have to fix up the Monitoring MSDE instance by following this rather complex KB Article:  http://support.microsoft.com/kb/918767

I also found this great how-to for upgrading SharePoint to SQL 2005 if you're interested:
http://www.sbslinks.com/sql2005.htm

Jeff
TechSoEasy
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Ahh... I knew I had seen this somewhere and just remembered where...

http://www.eventid.net/display.asp?eventid=4104&eventno=5254&source=SmallBusinessServer&phase=1

It has all the steps needed to reinstall Monitoring correctly including the few bits at the end about MSDE SP4.

Jeff
TechSoEasy
0
 
PortableLightingAuthor Commented:
TechSoEasy,

I already upgraded Sharepoint to SQL2005. It wasn't to bad.

I will look into the article on fixing the MSDE.

Most of this is in effort to get my tape backups squared away. I didn't want to install the SQL backup agent until I got all of the SQL issues repaired.

Thanks for your help.
0
 
PortableLightingAuthor Commented:
OK, I applied the command line setup for upgrading the instance to MSDE SP4. Everything appears to be good with it.
Of course everything appeared to running smoothly before the command line.

0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Well, reapplying a Service Pack never hurts.
Did you reinstall the Monitoring Components with the wizard in the Server Management Console?  

Jeff
TechSoEasy
0
 
PortableLightingAuthor Commented:
Yes, I did re-install the monitoring components sucessfully.

And as an added bonus, it seemd to fix the reports module in the CRM as well.

I did not know it wasn't working until our accountant  pointed out that the reports were working now.

I also just installed PowerEdge Server managment tools.

Next step is to install/configure the SQL Backup and Exchange Backup agents to get the DR plan in place.
0
 
PortableLightingAuthor Commented:
Thanks TechSoEasy, it looks like everything has installed correctly.
0

Featured Post

Free learning courses: Active Directory Deep Dive

Get a firm grasp on your IT environment when you learn Active Directory best practices with Veeam! Watch all, or choose any amount, of this three-part webinar series to improve your skills. From the basics to virtualization and backup, we got you covered.

  • 10
  • 8
Tackle projects and never again get stuck behind a technical roadblock.
Join Now