v-terliu
Fri Mar 28 04:40:47 PDT 2008
Hello Ken,
Thank you for your update.
I agree with you, the FRS should not happen on a single DC. However, I
still suggest you set the register key BurFlags to D2 as the following KB:
You cannot replicate files from a Windows Server 2003-based domain
controller and events are logged in the File Replication Service log
http://support.microsoft.com/?id=925633
If this unable to resolve this issue, you can set it to D4 for a test. If
all values unable to resolve this issue, please set it to back to original
value.
Note: Please try to backup your SBS before you modify the register key.
Backing Up and Restoring Windows Small Business Server 2003
http://go.microsoft.com/fwlink/?LinkId=49916
Meanwhile, I also suggest you perform the following steps:
1. Please rerun the CEICW to make sure your SBS 2003 server have right
network configuration. Go through the follow KB and rerun CEICW carefully.
How to configure Internet access in Windows Small Business Server 2003
http://support.microsoft.com/kb/825763/en-us
Detailed steps for your reference:
a. On the SBS 2003 Server open the Server Management console. Go to
Standard Management\To Do List.
b. Click the "Connect to the Internet" link.
c. When navigating to the Firewall page, select "Enable firewall" and click
Next.
d. On the "Services Configuration" page, select all the items and then
click Next.
e. On the "Web Services Configuration" page, make sure "Allow access to the
entire Web site from the Internet" is selected. If you select "Allow access
to only the following Web site services from the Internet", make sure all
items in the list are selected. Click Next.
f. On the "Web Server Certificate" page, choose to create a new Web server
certificate and then type the public domain name (your public DNS name)
that you will use to access OWA and RWW (for example, if your public domain
name that you use to access the sites is www.xyz.com, you should type
www.xyz.com as the new certificate name).
g. Go through the remaining steps.
2. Please ensure the DNS settings of SBS internal and external NICs are
pointing to SBS internal IP address.
I hope these steps will give you some help.
Thanks and have a nice day!
Best regards,
Terence Liu(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: NTFRS 13552 and 13555 Erorrs on SBS 2003 Following Tornado
| thread-index: AciP9hLFClKeNlOfRKq2+iFjppUqPg==
| X-WBNR-Posting-Host: 207.46.192.207
| From: =?Utf-8?B?c2hlcGNvbg==?= <shepcon@discussions.microsoft.com>
| References: <AA5B8A5C-1F14-4078-AD25-A6310FCF91D6@microsoft.com>
<eD1e2n1jIHA.4120@TK2MSFTNGP06.phx.gbl>
<7AF84824-7A47-4416-B46A-8F8DAF582717@microsoft.com>
<C4ow3I$jIHA.4200@TK2MSFTNGHUB02.phx.gbl>
| Subject: Re: NTFRS 13552 and 13555 Erorrs on SBS 2003 Following Tornado
| Date: Thu, 27 Mar 2008 03:34:01 -0700
| Lines: 222
| Message-ID: <E035C552-311F-45B1-8024-AAF3556853A4@microsoft.com>
| 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.2992
| Newsgroups: microsoft.public.windows.server.sbs
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:100124
| NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
| X-Tomcat-NG: microsoft.public.windows.server.sbs
|
| Thanks for your reply, Terence.
|
| I do have one further question for you, however. In your suggestion, you
| advise to set the BurFlags key to D2, which will pull/restore the data
from
| another known-good DC. But I only have the one DC, which is my SBS 2003
| Premium server and we know that its FRS data is bad. Should I use D4 as
the
| BurFlags key instead with my single DC? This is the part that I'm
somewhat
| confused about in reading the MS-KBs.
|
| Thanks.
|
| Ken
|
| "Terence Liu [MSFT]" wrote:
|
| > Hello Ken,
| >
| > Thank you for posting here.
| >
| > According to your description, I understand that you get event errors
13552
| > and 13555 about NTFRS on your SBS 2003. If I have misunderstood the
| > problem, please don't hesitate to let me know.
| >
| > Based on my research, I suggest we try the following steps to see if we
can
| > resolve this issue:
| >
| > I. This problem occurs when a file ID for data in the FRS database does
not
| > match the file ID for the data in the update sequence number (USN)
journal
| > database.
| >
| > To work around this problem, restore the SYSVOL data from a domain
| > controller that can replicate files to the domain controller that
cannot
| > replicate files. Use the non-authoritative method to restore this data.
For
| > more information about how to rebuild SYSVOL data, click the following
| > article number to view the article in the Microsoft Knowledge Base:
| >
| > How to rebuild the SYSVOL tree and its content in a domain
| >
http://support.microsoft.com/?id=315457
| >
| > To back up and restore the SYSVOL data, follow these steps: 1. Back up
the
| > following folders in a temporary location that is not in the SYSVOL
folder:
| >
| > a. %SystemRoot% \SYSVOL\Domain\Policies
| > b. %SystemRoot% \SYSVOL\Domain\Scripts
| >
| > Note: To retain the permissions for these folders, back up these
folders in
| > a location that is on the same volume as the SYSVOL folder.
| >
| > 2. Perform a non-authoritative restore on this replica set. To do
this,
| > follow these steps:
| >
| > a. Click Start, click Run, type cmd , and then click OK.
| > b. At the command prompt, type the following command, and then press
| > ENTER:
| >
| > net stop ntfrs
| >
| > c. Click Start, click Run, type regedit , and then click OK.
| > d. Locate and then click the following registry subkey:
| >
| >
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NtFrs\Parameters\Backup
| > /Restore\Process at Startup
| >
| > e. Right-click the BurFlags entry, and then click Modify.
| > f. In the Value data box, type D2 , and then click OK.
| > g. On the File menu, click Exit.
| > h. At the command prompt, type the following command, and then press
| > ENTER:
| >
| > net start ntfrs
| >
| > II. If the issue persists, I suggest you:
| >
| > 1. Stop NetLogon and FRS on the domain controller.
| >
| > 2. Delete the Ntfrs.jdb file in the <Windir>\Ntfrs\Jet folder.
| >
| > 3. Delete the Edb.chk file in the <Windir>\Ntfrs\Jet\Sys folder.
| >
| > 4. Delete the Edb.log file, the Res1.log file, and the Res2.log file in
| > the<Windir>\Ntfrs\Jet\Log folder.
| >
| > 5. Restart the NetLogon and FRS services on the domain controller.
| >
| > If we cannot resolve the issue after we perform the above steps, please
| > help me collect some information for further investigation:
| >
| > Gather MPS network report on SBS:
| >
| > a. Download MPSrepot_network from
| >
http://download.microsoft.com/download/b/b/1/bb139fcb-4aac-4fe5-a579-30b0bd9
| > 15706/MPSRPT_NETWORK.EXE
| >
| > b. Run MPSRPT_NETWORK.exe.
| >
| > c. The tool will automatically collect the information. This procedure
will
| > take 10~15 minutes.
| >
| > d. Open Windows Explorer, navigate to the folder:
| > %SystemRoot%\MPSReports\Network\Reports\Cab\
| >
| > e. Send the .cab file directly to me at v-terliu@microsoft.com
| >
| > I hope these steps will give you some help.
| >
| > Thanks and have a nice day!
| >
| > Best regards,
| >
| > Terence Liu(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: NTFRS 13552 and 13555 Erorrs on SBS 2003 Following
Tornado
| > | thread-index: AciPWyhAPZH2liPOQL63x512yRknwA==
| > | X-WBNR-Posting-Host: 207.46.19.168
| > | From: =?Utf-8?B?c2hlcGNvbg==?= <shepcon@discussions.microsoft.com>
| > | References: <AA5B8A5C-1F14-4078-AD25-A6310FCF91D6@microsoft.com>
| > <eD1e2n1jIHA.4120@TK2MSFTNGP06.phx.gbl>
| > | Subject: Re: NTFRS 13552 and 13555 Erorrs on SBS 2003 Following
Tornado
| > | Date: Wed, 26 Mar 2008 09:05:06 -0700
| > | Lines: 47
| > | Message-ID: <7AF84824-7A47-4416-B46A-8F8DAF582717@microsoft.com>
| > | 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.2992
| > | Newsgroups: microsoft.public.windows.server.sbs
| > | Path: TK2MSFTNGHUB02.phx.gbl
| > | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:99974
| > | NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
| > | X-Tomcat-NG: microsoft.public.windows.server.sbs
| > |
| > | PowerChute is installed and running correctly on the server.
However,
| > there
| > | was such an enormous amount of energy with the lightning and the
power
| > kept
| > | cycling, which seemed to overwhelm PowerChute. That's my guess
anyway.
| > At
| > | this point, it's water under the bridge.
| > |
| > | Ken
| > |
| > | "Lanwench [MVP - Exchange]" wrote:
| > |
| > | > shepcon <shepcon@discussions.microsoft.com> wrote:
| > | > > I'm running SBS 2003 Premium w/sp2 (not R2). A few weeks back, we
| > | > > were hit by the tornado that came through Atlanta and the server
| > | > > sustained a shutdown due to power events that overwhelmed our APC
| > | > > UPS.
| > | >
| > | > Ouch. But didn't your UPS simply shut down your server? Are you
| > running
| > | > PowerChute?
| > | >
| > | > > Following the event, I'm now getting several NTFRS 13552 and
| > | > > 13555 errors in my SBS event log. The FRS error status is
| > | > > FrsErrorMismatchedJournalId. I've done a good bit of research on
| > | > > these errors, but I'd like to get some feedback from the SBS gang
to
| > | > > correct the issue.
| > | > >
| > | > > Currently, the FRS service will start, but it will post these
errors
| > | > > in the event log. The SYSVOL and NETLOGON shares are functioning
| > | > > properly and the users can login just fine on the network. Also,
my
| > | > > SBS Group Policies are working fine. I do not have any other
domain
| > | > > controllers, but I do have one member server running MS-Windows
2003
| > | > > Server w/sp2. Symantec AV is set to exclude the necessary folders
| > | > > from realtime scanniing like SYSVOL. I do also have a good
backup of
| > | > > the SystemState from before the store with Veritas Backup Exec
9.1.
| > | > >
| > | > > What would be the best recommendation to correct this issue. I'm
| > | > > guessing that I can perform a non-authoritative restore using my
| > | > > backups of the SystemState, but I'd like to try the baby steps
first.
| > | > >
| > | > > Thanks for any guidance.
| > | > >
| > | > > Ken
| > | >
| > | > I'd probably start by checking out the event errors at
www.eventid.net
| > (well
| > | > worth a subscription) and look there -
| > | >
| > | >
| > | >
| > | >
| > |
| >
| >
|