RE: How do I get back to base SQL server on my SBS 2003 server?
- From: DanDan <DanDan@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 9 Aug 2007 08:44:03 -0700
The error is "fatal error on install" or something like it.
On reboot, the error is: "SQL Server Installation is either corrupt or has
been tampered with (unable to load SQLBOOT.DLL). Please uninstall then rerun
set up.
Can I reinstall the files from another SBS2003 server I manage?
On my install of SLQ2005, I told it to upgrade all instances.
So, how do I get back to ground zero?
Dan
--
the IT guy for small business
"Robert Li [MSFT]" wrote:
.
Hello Dan,
Thanks for posting in our newsgroup.
Please let me know the following to make the situation more clearly:
1. What's the error message you see when installing SQL?
2. Does Company work fine after the reinstallation?
First, since installation of SQL broke many applications and affects you
business, a suggestion is to call CSS directory who will provide you more
rapid and effective support. For the third party software, you need to
contact the software manufacture for more help. Thanks for your
understanding.
Also, the easier way is to restore the server from recent backup.
More info:
Backing Up and Restoring Windows Small Business Server 2003
http://www.microsoft.com/downloads/details.aspx?FamilyID=487736f8-f6f5-436d-
a82d-0c8d66e2a634&DisplayLang=en
Please make sure you fully took the steps in the following article:
Installing SQL Server 2005 WorkGroup Edition in Windows Small Business
Server 2003 R2
http://download.microsoft.com/download/4/0/8/40860507-c351-4308-a876-e1b83ee
4e77a/sqlinstallsteps.htm#BKMK_INSTALLNEWSQL
Before you install SQL Server 2005, review the following points:
1. Do not upgrade the instance of MSDE that is installed for Monitoring
(MSSQL$SBSMONITORING), because this it is not supported.
2. o not upgrade the instance of MSDE that is installed for Update Services
(MSSQL$WSUS), because this is not supported.
3. Do not migrate the instance of MSDE that is installed for Internet
Security and Acceleration (ISA) Server 2004 (MSSQL$MSFW), because this is
not supported on Windows SBS 2003 at this time.
4. Only SHAREPOINT instance can be upgraded to SQL Server 2005 Workgroup
Edition.
If the problem persists, please help me collect the following information
for further research:
1. Zip the "C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files" folder and send to me.
2. Screen shot of the error when you install SQL 2005 Workgroup edition.
Please send the information to v-robeli@xxxxxxxxxxxxx with subject:
40101333-How do I get back to base SQL server on my SBS 2003 server.
I am looking forward to hear from you.
If you need further assistance, please don't hesitate to let me know.
Best regards,
Robert Li(MSFT)
Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security
=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.
Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.
For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.
Any input or comments in this thread are highly appreciated.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
<Thread-Topic: How do I get back to base SQL server on my SBS 2003 server?
<thread-index: AcfYQyDQ5HUJDR0RTDuKqJv9TGdU/A==
<X-WBNR-Posting-Host: 207.46.193.207
<From: =?Utf-8?B?RGFuRGFu?= <DanDan@xxxxxxxxxxxxxxxxxxxxxxxxx>
<Subject: How do I get back to base SQL server on my SBS 2003 server?
<Date: Mon, 6 Aug 2007 09:02:02 -0700
<Lines: 52
<Message-ID: <8DBE08A9-CE00-419D-AADB-E51CF7ED2C5E@xxxxxxxxxxxxx>
<MIME-Version: 1.0
<Content-Type: text/plain;
< charset="Utf-8"
<Content-Transfer-Encoding: 7bit
<X-Newsreader: Microsoft CDO for Windows 2000
<Content-Class: urn:content-classes:message
<Importance: normal
<Priority: normal
<X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2826
<Newsgroups: microsoft.public.windows.server.sbs
<Path: TK2MSFTNGHUB02.phx.gbl
<Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:54742
<NNTP-Posting-Host: tk2msftsbfm01.phx.gbl 10.40.244.148
<X-Tomcat-NG: microsoft.public.windows.server.sbs
<
<I have been fighting this for several days.
<
<I have SBS 2003 R2 Premium on a Dell PowerEdge 2900, dual processor that
has
<been in production since November 06, running fine.
<
<The server-based applications that were running fine are: McAFee EPO,
<enterprise anti-virus and personal firewall, Backup Exec 11.d, SQL 2005
and
<ISA 2004 servers (the editions that came with Premium).
<
<Abount a month ago, MAS90 from Sage was installed by another consultant.
At
<that time, the admin password for McAfee stopped working. I inquired
about
<the MAS90 install and was told it had no impact on SQL. I later
remembered,
<that MAS90 runs on Pervasive SQL, but "should" run okay side-by-side. At
<that time, I realized that EPO would not let me in, but I thought that it
was
<because I had gotten clever with the admin password and needed to track it
<down.
<
<Wednesday, the CFO asked me to add a new PC to the antivirus push. So, it
<was time to resolve the issue. We opened a case with McAfee about the
<malfunctioning password. We could either send in a technical report, or
<simply "remove and install the server, which would be the quick and easy
way".
<
<I unistalled the EPO server via Add Remove Programs. I re-installed EPO
and
<selected to use the existing instance - because my SQL2005 install had
<upgraded all my instances.
<
<ISA2004 stopped passing internet traffic, maybe before I re-installed EPO.
<I uninstalled EPO. Re-installed with a new instance of the server. No
<change.
<I un-installed ISA2004. The internet came available. But not passive
ftp.
<(I had to clear the check for read-only ftp in ISA2004, but do not know
where
<that might be in the remaining def Windows firewall)
<I attempted to uninstall SQL2005 and start from base SQL.
<I removed the BKUPEXEC, SHAREPOINT, EPOSERVER instances believing I could
<reinstall them when needed.
<
<I followed kb909967 to manually uninstall SQL2005.
<I followed kb829114 to remove and re-install Sharepoint and companyweb.
<
<I now have a server that does not allow me to re-install SQL2005, does not
<let me re-install EPO and does not let me install Backup Exec.
<
<How can I un-install my way back to sanity?
<
<Thanks.
<
<
<--
<the IT guy for small business
<
<--
<the IT guy for small business
<
- Follow-Ups:
- RE: How do I get back to base SQL server on my SBS 2003 server?
- From: Robert Li [MSFT]
- RE: How do I get back to base SQL server on my SBS 2003 server?
- References:
- RE: How do I get back to base SQL server on my SBS 2003 server?
- From: Robert Li [MSFT]
- RE: How do I get back to base SQL server on my SBS 2003 server?
- Prev by Date: Re: Additional Exchange Server
- Next by Date: Re: Remote Assistance Not Working
- Previous by thread: RE: How do I get back to base SQL server on my SBS 2003 server?
- Next by thread: RE: How do I get back to base SQL server on my SBS 2003 server?
- Index(es):
Relevant Pages
|
