Welcome to ServerForumz.com!
FAQFAQ      ProfileProfile    Private MessagesPrivate Messages   Log inLog in

SBS 2003 and member server W2000 problems

 
Goto page Previous  1, 2
   Windows Server (Home) -> Windows Small Business Server RSS
Next:  install with internal IP in a peer to peer?  
Author Message
Jeff Middleton [SBS-MVP]

External


Since: Mar 04, 2004
Posts: 76



(Msg. 16) Posted: Fri Jun 09, 2006 2:02 pm
Post subject: Re: SBS 2003 and member server W2000 problems [Login to view extended thread Info.]
Archived from groups: microsoft>public>windows>server>sbs (more info?)

I'm seeing some common symptom over the last year (not statistically
significant yet) that one of the more odd behavioral symptoms related to
SATA RAID controllers built onto motherboard is that you may see resource
problems that don't show a symptom other than the machine behavior going to
sludge or the event logs showing one or more services going into arrest.

I was really fishing to see if that might be related to this because find a
way to track it down better.




"Les Connor [SBS Community Member - SBS MVP]" <les.connor DeleteThis @DEL.cfive.ca>
wrote in message news:us256L1iGHA.1320@TK2MSFTNGP04.phx.gbl...
> What's this about, Jeff?
>
> --
> Les Connor [SBS Community Member - SBS MVP]
> -----------------------------------------------------------
> SBS Rocks !
> ----------------------
> "Tell me and I'll forget. Show me and I'll remember. Involve me and I'll
> understand." - Confucius
>
>
> "Jeff Middleton [SBS-MVP]" <jeff DeleteThis @cfisolutions.com> wrote in message
> news:u5oqcmqiGHA.4660@TK2MSFTNGP03.phx.gbl...
> > By any chance, is the new SBS 2003 server running on a SATA RAID
connected
> > on a motherboard based controller?
> >
> > - Jeff Middleton SBS-MVP
> > YCST DeleteThis @SBSmigration.com
> >
> >
> > "Stephanie W" <StephanieW DeleteThis @discussions.microsoft.com> wrote in message
> > news:3EECF48E-A3A7-4C58-9ECC-CC37A1E38243@microsoft.com...
> >> We did a legitimate upgrade from SBS2000.
> >>
> >> "MS User2006" wrote:
> >>
> >> > When you say you upgraded to SBS 2003 did you upgrade from a previous
> > SBS
> >> > version or did you just add the SBS 2003 server to the domain calling
> >> > it
> > an
> >> > upgrade?
> >> >
> >> > "Stephanie W" <StephanieW DeleteThis @discussions.microsoft.com> wrote in message
> >> > news:6EAEDB42-9FA4-4F43-9464-06D14FEA3DC5@microsoft.com...
> >> > > We recently upgraded to SBS2003 and all went well with the
> >> > > conversion.
> > We
> >> > > also have a W2000 server that is used solely for Macola. Ever
since
> > the
> >> > > conversion, the W2000 server freezes about once a week and becomes
> >> > > unresponsive. I receive no errors in the SBS event log and the
> > following
> >> > > in
> >> > > the member server application log. Stop event id 1000 Userenv -
> > Windows
> >> > > cannot obtain the Domain Controller name for your computer network.
> >> > > Return
> >> > > code value (59) and Warning event id 213 License Service -
> >> > > Replication
> > of
> >> > > license information failed because the License Logging Service on
> > server
> >> > > could not be contacted.
> >> > >
> >> > > I took the member server out of the Domain and then rejoined in the
> > hopes
> >> > > of
> >> > > a better connection, but this did not work. Once the member server
> >> > > is
> >> > > re-boot, the License Service message stops for a few days but then
> >> > > reappears.
> >> > > The Userenv error always appears.
> >> > >
> >> > > Does anyone have any suggestions? We keep incurring data
corruption
> > when
> >> > > the member server freezes.
> >> > >
> >> > > Thanks in advance
> >> >
> >> >
> >> >
> >
> >
>
>

 >> Stay informed about: SBS 2003 and member server W2000 problems 
Back to top
Login to vote
MPWCS

External


Since: Jun 26, 2007
Posts: 1



(Msg. 17) Posted: Tue Jun 26, 2007 7:54 am
Post subject: RE: SBS 2003 and member server W2000 problems [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

I am finding similar errors in my secondary DC and Member servers since
installing SBS 2003 premium.

Environment:

Primary DC:
Windows SBS 2003 premium w/sp1
Fresh install, joined to an existing domain.
All FSMO Roles held on SBS

Secindary DC:
Windows Server 2003 Standard
Upgraded from Windows Server 2000 Standard.
Holds terminal Server licensing for Citrix Server.

Member Server 1:
Windows 2000 standard Host OS
Citrix Metaframe Server

Member Server 2
Windows 2000 standard host OS
Used for SQL Server 2000 and internal web based program.

Errors appearing:
Event Type: Warning
Event Source: LicenseService
Event Category: None
Event ID: 213
Date: 6/25/2007
Time: 5:16:31 PM
User: N/A
Computer: [SERVER]
Description:
Replication of license information failed because the License Logging
Service on server [servername]
could not be contacted.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 22 00 00 c0 "..À


The article referenced in the error applies to a server that has been
demoted from DC status to Member status, this does not apply in my
environment.

the above error is appreaing on the 2nd DC and both member servers.
Other information that appears to be related:

The SBS Server's License Logging Service is logging on as
NT AUTHORITY\NetworkService

All other servers are using "Local System Account"
I am not able to change the other servers to use the NT
Authority\NetworkService account to match the SBS server and have not
attempted to use the local system account on the sbs server.

There are no other errors / warnings related to licensing or replication
issues in any of the other logs.

Stephanie may want to look in the licensing configuration for the other
servers to ensure they use Per Device /Per user licensing. rather than per
server licensing.



I would appreciate it if someone could verify which account I should be
using for this service to enable replication. I have been using the defaults
so far and they are obviously not working properly.


"Stephanie W" wrote:

> We recently upgraded to SBS2003 and all went well with the conversion. We
> also have a W2000 server that is used solely for Macola. Ever since the
> conversion, the W2000 server freezes about once a week and becomes
> unresponsive. I receive no errors in the SBS event log and the following in
> the member server application log. Stop event id 1000 Userenv - Windows
> cannot obtain the Domain Controller name for your computer network. Return
> code value (59) and Warning event id 213 License Service - Replication of
> license information failed because the License Logging Service on server
> could not be contacted.
>
> I took the member server out of the Domain and then rejoined in the hopes of
> a better connection, but this did not work. Once the member server is
> re-boot, the License Service message stops for a few days but then reappears.
> The Userenv error always appears.
>
> Does anyone have any suggestions? We keep incurring data corruption when
> the member server freezes.
>
> Thanks in advance

 >> Stay informed about: SBS 2003 and member server W2000 problems 
Back to top
Login to vote
Display posts from previous:   
   Windows Server (Home) -> Windows Small Business Server All times are: Pacific Time (US & Canada) (change)
Goto page Previous  1, 2
Page 2 of 2

 
You can post new topics in this forum
You can reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum



[ Contact us | Terms of Service/Privacy Policy ]