RE: Backup and Sharepoint

Thankyou Jenny for the input.

I can confirm that Backup still fails after your recommendations.

Do I just try and redo the SBS Sp1 on its own again, ie. just SBS2003 SP1 or
do I need to do all 4 service packs.

DCOM issue. Do I fix before or should I leave this until I have redone SBS SP1

Many thanks for your patience. This has been the most challenging Service
Pack I have ever encountered in all your products of the years from NT3.5

Regards

Alan

""Jenny wu [MSFT]"" wrote:

> Hi,
>
> Thanks for your update and information.
>
> For your application and system logs, there are some problems in your SBS
> server. I will help you troubleshooting the issue one by one and also you
> can create new threads to post other issues.
>
> Please note that 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.
>
> If this response time does not meet your needs, please contact CSS by phone
> call for more immediate assistance. For more information
> on available PSS services, please click here:
> http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607
>
> It is may be efficient method to reinstall SBS 2003 SP1. If you do that it
> is recommended you apply SBS sp1 follow installation guide provided by
> Microsoft and you will not encounter many issues.
>
> You can refer to the following link to apply SBS SP1:
> http://www.smallbizserver.net/Default.aspx?PageContentID=62&tabid=236
>
> In the following website you can find many useful resources related to SBS
> SP1:
> http://www.smallbizserver.net/Default.aspx?PageContentID=53&tabid=236
>
> The website includes: What is SP1 for SBS 2003 and what you need to know |
> Standard install step-by-step | Premium install step-by-step | Things to do
> after the upgrade | Errors that can occur after the upgrade
>
> Let use focus the backup issue, the VSS error code is very general, we can
> not isolate the root cause by it. Please try my suggestion in my previous
> post to try to resolve it.
>
> The DCOM error indicates there are some third party applications installed
> in your SBS server, such as McAfee. This event appears a program
> identified by the Clsid displayed in the message, tried to start the DCOM
> server by using the DCOM infrastructure. However, the permission associated
> with the DCOM Server was not correctly set up. you can refer to the
> following steps to resolve it:
>
> 1. Search for the registry key using {<CLSID>} which is mentioned in the
> event description and get the registry key xxx (for example).
> 2. Open the Component Services Administrative Tool -> My Computer -> DCOM
> Configuration. Point to "xxx" -> Properties (right click) -> Security Tab.
> Change "Launch and Activation Permissions" to Default or insert via the
> Custom tab the INTERACTIVE group and give it full access.
>
> I appreciate you time and efforts to perform test. I am currently standing
> by for your test result. I am looking forward to your reply.
>
> Have a nice day!
>
> Best Regards,
>
> Jenny Wu
> 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: Backup and Sharepoint
> >thread-index: AcWy6TRquDRslJ+FStGloyoRpYy5zQ==
> >X-WBNR-Posting-Host: 213.120.102.130
> >From: "=?Utf-8?B?QmlnQWw=?=" <BigAl@xxxxxxxxxxxxxxxxxxxxxxxxx>
> >References: <4B1F7674-A5E2-4225-A66A-8425F4852F24@xxxxxxxxxxxxx>
> <VnobgIfsFHA.3308@xxxxxxxxxxxxxxxxxxxxx>
> >Subject: RE: Backup and Sharepoint
> >Date: Tue, 6 Sep 2005 06:45:12 -0700
> >Lines: 279
> >Message-ID: <6F008D10-54B1-47F2-8EB3-18062B6B472B@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.0
> >Newsgroups: microsoft.public.windows.server.sbs
> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> >Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
> >Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:151176
> >X-Tomcat-NG: microsoft.public.windows.server.sbs
> >
> >Dear Jenny,
> >
> >I have sent you the logs as per the email given in your reply. I hope this
> >is correct as it appears different to your name.
> >
> >Please note the VSS error ID, I wonder if this has any bearing on all the
> >issues I have as it points to a Access Denied issue.
> >
> >Regards
> >
> >Alan
> >
> >""Jenny wu [MSFT]"" wrote:
> >
> >> Hi,
> >>
> >> Thanks for posting here!
> >>
> >> I am sorry for the delayed response due to weekend. Please understand
> that
> >> the newsgroups are staffed weekdays by Microsoft Support professionals
> to
> >> answer your systems and applications questions. Your understanding is
> >> greatly appreciated!
> >>
> >> Regarding your post, I understand that after you updated to SBS SP1 you
> >> encountered two issues: backup failed and sharepoint issue. If I am off
> >> base, please don't hesitate to let me know.
> >>
> >> Have you re-run CEICW after applied SBS SP1? Please rerun the wizard
> again
> >> to check if there is any error during doing this. If yes, give me a
> screen
> >> shot of the error message. If not, please try to test, does issues be
> fixed?
> >>
> >> Let us try to resolve your issues one by one so that we can sort out the
> >> root cause.
> >>
> >> Backup issue:
> >> ==============================
> >> I. After I research some cases, I found the issue can occur if there is
> >> another server on the network thought that it was also the PDC for your
> >> domain. This conflict caused service failures on the SBS server.
> >> Please follow my suggestion to try to resolve the issue:
> >>
> >> 1. Please check if there is another domain controller or server in the
> >> network was claiming to be the Primary Domain Controller in the Network.
> If
> >> yes, please remove the problematic computer from the network but
> shutting
> >> down the machine.
> >>
> >> If it is not your situation, please try follows.
> >>
> >> 2. Please re-register VSS. To re-register VSS, you run the following
> >> commands while you're in the \%systemroot%\system32 directory at the
> >> command prompt:
> >>
> >> ***regsvr32 ole32.dll
> >> ***regsvr32 vss_ps.dll
> >> ***Vssvc /Register
> >> ***regsvr32 /i swprv.dll
> >> ***rRegsvr32 /i eventcls.dll
> >> ***regsvr32 es.dll
> >> ***regsvr32 stdprov.dll
> >> ***regsvr32 vssui.dll
> >> ***regsvr32 msxml.dll
> >> ***regsvr32 msxml3.dll
> >> ***regsvr32 msxml4.dll
> >>
> >> And then reset IIS, try to test, how about the result?
> >>
> >> II. The issue can also be caused by the incorrect content of the
> >> "script.bks" file.
> >>
> >> Open the Small Business Backup Script.bks file with the notepad. If you
> see
> >> this word: JET SERVERNAME\Microsoft Information Store\Recovery Storage
> >> Group\ , this problem will appear because NTbackup is not able to back
> up
> >> the Recovery Storage Group either via the script or directly via the
> >> NTbackup GUI. To correct it, you can use NTbackup to remove Recovery
> >> Storage Group reference from the backup selection script:
> >> 1. Start -> Run -> NTBackup -> Advanced Mode -> Backup tab -> Job ->
> Load
> >> Selections.
> >> 2. Select Small Business Backup Script.bks
> >> 3. Click OK on the error message: "Some invalid selections found in
> >> C:\Program Files\Microsoft Windows Small Business Server\Backup\Small
> >> Business Backup Script.bks".
> >> 4. Job -> Save Selections".
> >>
> >> Try to test, does the issue be fixed?
> >>
> >> III. Disable the Exchange writer by editing the registry under
> >>
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\Parameters
> >> System: please try to the following KB article to do that:
> >> How to turn on the Exchange writer for the Volume Shadow Copy service in
> >> Windows Small Business Server 2003
> >> http://support.microsoft.com/?kbid=838183
> >>
> >> Try to test, how about the result?
> >>
> >> IV. Clean the tape, and then go to RSM to mark the tape as 'Clean'. Can
> the
> >> backup run successfully then? We've seen some issues that the Windows
> >> service pack 1 does not recognize the media until the tape drive was
> >> "cleaned" (or marked as clean).
> >>
> >> Try to test, how about the result?
> >>
> >> V. Uninstall the tape drive and remove it from the libraries, and then
> scan
> >> the computer for the hardware changes. Once the hardware is detected,
> >> reinstall the latest driver. Try to test, how about the result?
> >>
> >> VI. Check if there's an updated driver and firmware for the device, if
> so,
> >> apply it. Try to test, how about the result?
> >>
> >> VII. Rebuild the RSM database. Please refer to the following steps:
> >>
> >> 1. Stop the RSM Service.
> >> 2. Delete the RSM databases located at %SystemRoot%\System32\NtmsData.
> >> 3. Restart the RSM Service, this will recreate new, empty RSM Databases.
>
> >> 4. Put a new tape in, or a tape that may be deleted.
> >> 5. Go to the "properties" of the disk inside the physical locations.
> >> Uncheck 'Enable Drive' Hit apply & then check the 'Enable Drive' again
> >> (This was done to reset the Flag since we had renamed the database for
> RSM)
> >>
> >> 6. Right click, and prepare.
> >>
> >> - This will delete it, write a media label to it, add it to the Free
> Media
> >> Pool.
> >> Try to test, how about the result?
> >>
> >> If the issue persists, please help me collect some information to
> further
> >> analyze the issue:
> >>
> >> 1. Can you get any error event log in the Event Viewer? Please give me
> all
> >> the accurate error event information.
> >> 2. Can you successfully access the Backup snap-in in the SBS Management
> >> console?
> >> 3. Please give me the Backupxx.log and Sbsbackuplog0x.log logs to
> further
> >> troubleshoot the issue. You can send it to my mailbox:
> >> v-yanniw@xxxxxxxxxxxxx
> >>
> >> *The Backupxx.log files in the folder "C:\Documents and Settings\SBS
> Backup
> >> User\Local Settings\Application Data\Microsoft\Windows NT\NTBackup\data".
> >>
> >> [Note] Before reproduce the problem, please open NTBACKUP, click
> >> "Tools"->"Options" and then check "Detailed" on the "Backup Log" tab.
> Then
> >> reproduce this issue and send the backup log to me (Tools->Report).
> >>
> >> *The Sbsbackuplog0x.log files which can be located under the folder
> >> "%sbsprogramdir%\Support\Backup Logs".
> >>
> >> Sharepoint issue:
> >> =================
> >> To the Sharepoint issue, please help me collect some information:
> >>
> >> 1. Can you open Sharepoint Central Administration (Start ->
> Administrative
> >> Tools -> Sharepoint Central Administration) using Administrator account?
> >> 2. Please check if the services MSSQl$SHAREPOINT service is running in
> >> services console, please stop it and restart it. Try to test.
> >> 3. Please Locate, and then click the following registry subkey:
> >> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SPTimer
> >> Ensure MSSQL$SHAREPOINT in the Value data box.
> >>
> >> 4. Please check file permissions on C:\Program Files\Common
> >> Files\System\Ole DB\oledb32.dll
> >> Ensure the permission as follows:
> >> Administrators (Full Control)
> >> SYSTEM (Full Control)
> >> Users (Read & Execute)
> >> After changing permission please try to restart MSSQL$SHAREPOINT service
.

Relevant Pages

  • RE: ASR + error message "Setup was unable to format the drive"
    ... First of all, for SBS backup, we do not recommend you to use ASR. ...
    (microsoft.public.windows.server.sbs)
  • Re: Removeable Storage Error
    ... It means that some settings in DCOM for Removable Storage are not ... it wanted to register two GUID's that were listed in DCOM but not the AppID ... Les Connor [SBS MVP] ... >>>last backup failed, ...
    (microsoft.public.windows.server.sbs)
  • Re: Removable Storage - Snapin
    ... I thought DCOM was pretty good at logging errors, though - so there would be ... Les Connor [SBS Community Member - SBS MVP] ... > Will leave tonight as need to get a good backup before delving too deep. ... >>> THE SNAPIN'S DISPLAY MAY BE INCONSISTANT WITH THE REMOVABLE STORAGE ...
    (microsoft.public.windows.server.sbs)
  • Re: Removable Storage - Snapin
    ... You cannot successfully mount a tape drive on a Windows Server 2003-based ... Merv Porter [SBS MVP] ... > backup completes. ... >>I thought DCOM was pretty good at logging errors, ...
    (microsoft.public.windows.server.sbs)
  • RE: SBS Backup problems
    ... other application service) installed on the SBS 2003 server? ... So I would not think this could be the reason for backup ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
Loading