Re: Problems after SBS_SP1
- From: "Brian E. Goldman" <bgoldman@xxxxxxxxxxxxx>
- Date: Sat, 11 Jun 2005 14:30:51 -0400
I'm having a similar problem of re-installing from CD3...did you copy the
files from the original CD3 or from an extracted file?
This has been really confusing. Microsoft has got to do better job.
"Bjørn Johannessen" <bjorn@xxxxxxxxxxxxxxxxx> wrote in message
news:uQVj4plbFHA.2288@xxxxxxxxxxxxxxxxxxxxxxx
> Ok , I found out that the extracted folder did not contain any sharepoint
> inst. files, just the folder and a compressed file.. I copied files from
> the CD3 to the extracted folder and all went
> well.
>
>
>
> ....and voila ! SP1 installed withouth errors !! ;-))
>
> Thank you very much to both Nathan and Steven .
> BJ
>
> "Nathan Liu [MSFT]" <v-natliu@xxxxxxxxxxxxxxxxxxxx> wrote in message
> news:wodZJGbbFHA.3052@xxxxxxxxxxxxxxxxxxxxxxxx
>> Hello Bjorn,
>>
>> Thank you for your update.
>>
>> I'm so sorry for my delay, I need more times to do deep research and
>> testing. Many thanks for your understanding.
>>
>> According to your description, I understand that you are prompted for SBS
>> disk 3 with SBS SP1 when you reinstalling the Sharepoint service
>> companyweb
>> component. If I have misunderstood your concern, please don't hesitate to
>> let me know.
>>
>> Based on my deep research, I found the SBSMONITORING CSDVersion register
>> key in the below:
>>
>> [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
>> Server\SBSMONITORING\MSSQLServer\CurrentVersion]
>> "CurrentVersion"="8.00.194"
>> "RegisteredOwner"=""
>> "SerialNumber"=""
>> "CSDVersionNumber"=dword:00000300
>> "CSDVersion"="8.00.761"
>> "Language"=dword:00000409
>>
>> The "CSDVersion"="8.00.761" is version of MSDE SP3a, so you also need to
>> upgrade the MSDE 2000 to MSDE 2000 SP4. We need to reinstall the
>> Companyweb
>> and Monitoring components, and then re-apply Small Business Server 2003
>> SP1.
>>
>> I. Please refer to the KB article 829114 to remove the Companweb
>> component. (According to your previous reply, I know you already finished
>> these steps. Please skip to the next step.)
>>
>>
>> II. Please perform the following steps to remove the Monitoring
>> component.
>>
>> A. Uninstall Monitoring
>>
>> 1. Click Start, click Control Panel, and then click Add or Remove
>> Programs.
>>
>> 2. Select Windows Small Business Server 2003 and then click
>> Change/Remove. The Setup Wizard appears.
>>
>> 3. Click Next to start the wizard.
>>
>> 4. On the Windows Configuration page, click Next.
>>
>> 5. On the Component Selection page, in the Action column, change
>> Server Tools to Maintenance, change Monitoring component to Remove, and
>> then click Next.
>>
>> 6. On the Component Summary page, click Next.
>>
>> 7. Click Finish.
>>
>>
>> B. Uninstall Microsoft SQL Server Desktop Engine (SBSMONITORING)
>>
>> In Add or Remove Programs, select Microsoft SQL Server Desktop Engine
>> (SBSMONITORING) and then click Remove. A dialog box appears. To confirm
>> that you want to remove, click Yes.
>>
>>
>> C. Rename the folder
>>
>> Start Windows Explorer, and then locate and rename the following folder:
>>
>> C:\Program Files\Microsoft SQL Server\MSSQL$SBSMONITORING
>>
>> to C:\Program Files\Microsoft SQL Server\MSSQL$SBSMONITORING.old
>>
>>
>> D. Use Registry Editor to delete the following registry key:
>>
>> HKEY_LOCAL_MACHINE\Software\Microsoft\SmallBusinessServer\Monitoring
>>
>> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\SBSMonitoring
>>
>>
>> III. Install Companweb and Monitoring components:
>>
>> 1. Click Start, point to Control Panel, and then click Add or Remove
>> Programs.
>>
>> 2. In the Currently installed programs list, click Microsoft Windows
>> Small Business Server 2003, and then click Change/Remove.
>>
>> 3. In the Microsoft Windows Small Business Server Setup Wizard, click
>> Next repeatedly until the Component Selection page is displayed.
>>
>> 4. In the Server Tools list, click Maintenance.
>>
>> 5. In the Intranet and Monitoring list, click Install.
>>
>> 6. At the Logon Information screen, click Log on automatically, and
>> then
>> type your password for the user account that you currently are logged on
>> with.
>>
>> When you are prompted for SBS disk 3 with SBS SP1, please refer to the
>> following Workaround:
>>
>> Workaround
>>
>> We need to extract SBS SP1 installation folders, and then point the SBS
>> Integrated setup program to the folder for the 'SP1 CD3' contents.
>>
>> The extraction process is listed below, please do follow the exact steps
>> or
>> the extracted files will be removed. ?
>>
>> 1. Start a cmd prompt and change directory to the SP1 download folder
>> (or the SBS03_SP1 folder on PKG_CD2).
>>
>> 2. Then key 'SBS2003-KB885918-SP1-X86-ENU.EXE /?', the installer
>> extracts files into a guid-like folder name, on my box, it's
>> C:\b5469c25ed0a876e198de1b10efc.
>>
>> 3. Meanwhile, the help message box is displayed. Do not click OK, or
>> the
>> GUID-like folder will vanish.
>>
>> 4. Instead, we go to 'Task Manager', end the process
>> 'SBS2003-KB885918-SP1-X86-ENU.EXE' first, then, end the 'update.exe'
>> process. By doing this, the install folder will remain on your hard disk.
>> Note that you need to end these 2 process in turn.
>>
>> 5. Now go the download or CD folder which contains
>> SBS2003-KB891193-X86-ENU.EXE. Open up a command console and issue
>> 'SBS2003-KB891193-X86-ENU.EXE /?'.
>>
>> 6. The files will be extracted to another GUID-like folder and the
>> Help
>> window comes up. Again, we will not click OK on the Help window.
>>
>> 7. Go to 'Task Manager', and then end the process '
>> SBS2003-KB891193-X86-ENU.EXE' and 'update.exe' in turn. That will end the
>> install process without cleaning up the extracted files.
>>
>> 8. Run the SBS Integrated setup, and when the setup program prompts
>> for
>> the CD3, point it to the GUID folder created above. If the first folder
>> doesn't what the setup program wants, point to the second folder.
>>
>> After you finish the above steps, please restore the Companyweb and
>> Monitoring databases, these database files are located in the
>> MSSQL$SHAREPOINT.old and MSSQL$SBSMONITORING.old folder.
>>
>> IV. Re-apply SBS 2003 SP1. Please run the
>> SBS2003-KB885918-SP1-X86-ENU.EXE
>> to upgrade the SBSMonitoring MSDE and SharePoint WMSDE instances to their
>> respective SP4 level.
>>
>>
>> Otherwise, please help me gather more information for further
>> troubleshooting:
>>
>> 1. Please navigate the cnfgsvr.out from the C:\Program Files\Microsoft
>> SQL
>> Server\MSSQL$SBSMONITORING\Install folder, and send to me.
>>
>> 2. Please navigate the cnfgsvr.out from the C:\Program Files\Microsoft
>> SQL
>> Server\MSSQL$SHAREPOINT\Install folder, and send to me.
>>
>> 3. Please navigate C:\Program Files\Microsoft Windows Small Business
>> Server\Support\*.*, and send me the all files.
>>
>>
>> Again thanks for your time and patience in this matter. I'm looking
>> forward
>> to your update. If you have any questions or concerns, please do not
>> hesitate to let me know. I am always happy to be of further assistance.
>>
>> Best regards,
>>
>> Nathan Liu (MSFT)
>> Microsoft CSS Online Newsgroup Support
>> Get Secure! - www.microsoft.com/security
>> =====================================================
>> When responding to posts, please "Reply to Group" via your newsreader so
>> that others may learn and benefit from your issue.
>> =====================================================
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> --------------------
>>>From: "Steven Banks [SBS MVP]" <steve@xxxxxxxxxxxxxxxxxxxxxx>
>>>References: <uCO2rDhaFHA.580@xxxxxxxxxxxxxxxxxxxx>
>> <#ERfTOhaFHA.2076@xxxxxxxxxxxxxxxxxxxx>
>> <OYSPSplaFHA.3848@xxxxxxxxxxxxxxxxxxxx>
>> <#jdz8ZSbFHA.2440@xxxxxxxxxxxxxxxxxxxx>
>> <uZY$TWTbFHA.3184@xxxxxxxxxxxxxxxxxxxx>
>>>Subject: Re: Problems after SBS_SP1
>>>Date: Thu, 9 Jun 2005 19:02:46 -0700
>>>Lines: 164
>>>X-Priority: 3
>>>X-MSMail-Priority: Normal
>>>X-Newsreader: Microsoft Outlook Express 6.00.2900.2527
>>>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527
>>>X-RFC2646: Format=Flowed; Response
>>>Message-ID: <O#Zyr$VbFHA.2416@xxxxxxxxxxxxxxxxxxxx>
>>>Newsgroups: microsoft.public.windows.server.sbs
>>>NNTP-Posting-Host: corp.banksnw.com 168.103.172.60
>>>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP09.phx.gbl
>>>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:126077
>>>X-Tomcat-NG: microsoft.public.windows.server.sbs
>>>
>>>Bjorn,
>>>
>>>Per Wallace Fu at MSFT:
>>>
>>>You may need to extract SBS SP1 installation folders, and then point the
>> SBS
>>>Integrated setup program to the folder for the 'SP1 CD3' contents.
>>>
>>>
>>>
>>>The extraction process is listed below, please do follow the exact steps
>> or
>>>the extracted files will be removed.
>>>
>>>
>>>
>>> 1. Start a cmd prompt and change directory to the SP1
>>>download folder (or the SBS03_SP1 folder on PKG_CD2).
>>>
>>>
>>>
>>> 2. Then key 'SBS2003-KB885918-SP1-X86-ENU.EXE /?', the
>>>installer extracts files into a guid-like folder name, on my box, it's
>>>C:\b5469c25ed0a876e198de1b10efc.
>>>
>>>
>>>
>>> 3. Meanwhile, the help message box is displayed. Do not
>> click
>>>OK, or the GUID-like folder will vanish.
>>>
>>>
>>>
>>> 4. Instead, we go to 'Task Manager', end the process
>>>'SBS2003-KB885918-SP1-X86-ENU.EXE' first, then, end the 'update.exe'
>>>process. By doing this, the install folder will remain on your hard disk.
>>>Note that you need to end these 2 process in turn.
>>>
>>>
>>>
>>> 5. Now go the download or CD folder which contains
>>>SBS2003-KB891193-X86-ENU.EXE. Open up a command console and issue
>>>'SBS2003-KB891193-X86-ENU.EXE /?'.
>>>
>>>
>>>
>>> 6. The files will be extracted to another GUID-like folder
>>>and the Help window comes up. Again, we will not click OK on the Help
>>>window.
>>>
>>>
>>>
>>> 7. Go to 'Task Manager', and then end the process '
>>>SBS2003-KB891193-X86-ENU.EXE' and 'update.exe' in turn. That will end the
>>>install process without cleaning up the extracted files.
>>>
>>>
>>>
>>> 8. Run the SBS Integrated setup, and when the setup
>>> program
>>>prompts for the CD3, point it to the GUID folder created above. If the
>> first
>>>folder doesn't what the setup program wants, point to the second folder.
>>>
>>>
>>>
>>>Hope this does the trick for you Bjorn.
>>>Steve
>>>
>>>Steven Banks [SBS MVP]
>>>Banks Consulting Northwest Inc.
>>>http://www.banksnw.com
>>>
>>>
>>>"Bjørn Johannessen" <bjorn@xxxxxxxxxxxxxxxxx> wrote in message
>>>news:uZY$TWTbFHA.3184@xxxxxxxxxxxxxxxxxxxxxxx
>>>> Steven
>>>>
>>>> No, I was advised by Nathan to remove and re-install SharePoint
>> services,
>>>> but re-installing wont work because the installprogram asks for CD3
>> with
>>>> SP1 on it !!! I have only the old CD3 !
>>>>
>>>>
>>>> And here I am without sharepoint services ;-( and a SP1 that wont
>>>> install sql SP4 .........
>>>>
>>>>
>>>> BJ
>>>>
>>>> "Steven Banks [SBS MVP]" <steve@xxxxxxxxxxxxxxxxxxxxxx> wrote in
>>>> message
>>>> news:%23jdz8ZSbFHA.2440@xxxxxxxxxxxxxxxxxxxxxxx
>>>>> Bjorn,
>>>>>
>>>>> Sorry to leave you hanging. Did you get this resolved yet?
>>>>> Steve
>>>>>
>>>>> Steven Banks [SBS MVP]
>>>>> Banks Consulting Northwest Inc.
>>>>> http://www.banksnw.com
>>>>>
>>>>>
>>>>> "Bjørn Johannessen" <bjorn@xxxxxxxxxxxxxxxxx> wrote in message
>>>>> news:OYSPSplaFHA.3848@xxxxxxxxxxxxxxxxxxxxxxx
>>>>>> Steven
>>>>>>
>>>>>> I have lots of HD space , over 100GB . Tried to flush the temp
>> folder
>>>>>> but
>>>>>> still no luck..
>>>>>>
>>>>>> BJ
>>>>>>
>>>>>> "Steven Banks [SBS MVP]" <steve@xxxxxxxxxxxxxxxxxxxxxx> wrote in
>> message
>>>>>> news:%23ERfTOhaFHA.2076@xxxxxxxxxxxxxxxxxxxxxxx
>>>>>>> Hi Bjorn,
>>>>>>>
>>>>>>> How's your hard drive space? Another person had a similar error.
>> When
>>>>>>> he flushed the temp folder and reran the SP it was successful.
>>>>>>>
>>>>>>> Steve
>>>>>>>
>>>>>>> Steven Banks [SBS MVP]
>>>>>>> Banks Consulting Northwest Inc.
>>>>>>> http://www.banksnw.com
>>>>>>>
>>>>>>>
>>>>>>> "Bjørn Johannessen" <bjorn@xxxxxxxxxxxxxxxxx> wrote in message
>>>>>>> news:uCO2rDhaFHA.580@xxxxxxxxxxxxxxxxxxxxxxx
>>>>>>>>I have 2 problems after upgrading our SBS 2003 std to SP1. I
>> followed
>>>>>>>>the instructions at www.smallbizserver.net .
>>>>>>>>
>>>>>>>> sbsSP1 reported this error :
>>>>>>>>
>>>>>>>> Component Name: Server Configuration
>>>>>>>> Version: NA
>>>>>>>> Installation Status: Failure
>>>>>>>> Error Message: MSDE 2000 Service Pack 4 did not install. For
>>>>>>>> additional instructions, see the SQL Server 2000 Service Pack Web
>> site
>>>>>>>> at http://go.microsoft.com/fwlink/?LinkId=46241.
>>>>>>>>
>>>>>>>>
>>>>>>>> My second problem is logging into server using RWW "connect to
>> server
>>>>>>>> desktops ."
>>>>>>>>
>>>>>>>> If I try to : "Log on to or resume the console session of the
>>>>>>>> remote
>>>>>>>> computer" the server reboots after a "bluescreen"
>>>>>>>>
>>>>>>>> If I log on via RWW to the server without resuming a session ,
>>>>>>>> everything is OK.
>>>>>>>>
>>>>>>>> If I connect via VPN and connects to external server desktop
>>>>>>>> everything is OK.
>>>>>>>>
>>>>>>>> Anyone can help ?
>>>>>>>>
>>>>>>>> Thanks
>>>>>>>>
>>>>>>>> BJ
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
>
>
.
- Follow-Ups:
- Re: Problems after SBS_SP1
- From: Bjørn Johannessen
- Re: Problems after SBS_SP1
- References:
- Problems after SBS_SP1
- From: Bjørn Johannessen
- Re: Problems after SBS_SP1
- From: Steven Banks [SBS MVP]
- Re: Problems after SBS_SP1
- From: Bjørn Johannessen
- Re: Problems after SBS_SP1
- From: Steven Banks [SBS MVP]
- Re: Problems after SBS_SP1
- From: Bjørn Johannessen
- Re: Problems after SBS_SP1
- From: Steven Banks [SBS MVP]
- Re: Problems after SBS_SP1
- From: Nathan Liu [MSFT]
- Re: Problems after SBS_SP1
- From: Bjørn Johannessen
- Problems after SBS_SP1
- Prev by Date: Re: w32 Time, mad process consuming lots of memory
- Next by Date: Re: WSUS RTM breaks SBS 2003 SP1 reporting
- Previous by thread: Re: Problems after SBS_SP1
- Next by thread: Re: Problems after SBS_SP1
- Index(es):
Relevant Pages
|