|
Next: install with internal IP in a peer to peer?
|
| Author |
Message |
External
Since: Jun 07, 2006
Posts: 6
|
(Msg. 1) Posted: Wed Jun 07, 2006 9:37 am
Post subject: SBS 2003 and member server W2000 problems
Archived from groups: microsoft>public>windows>server>sbs (more info?)
|
|
|
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 |
|
| Back to top |
|
 | |
External
Since: May 30, 2006
Posts: 144
|
(Msg. 2) Posted: Wed Jun 07, 2006 9:47 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?)
|
|
|
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.RemoveThis@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 |
|
| Back to top |
|
| |
External
Since: Jun 07, 2006
Posts: 6
|
(Msg. 3) Posted: Wed Jun 07, 2006 11:57 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?)
|
|
|
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.TakeThisOut@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 |
|
| |
External
Since: May 30, 2006
Posts: 144
|
(Msg. 4) Posted: Wed Jun 07, 2006 12:02 pm
Post subject: Re: SBS 2003 and member server W2000 problems [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
When you upgraded to SBS 2003 you did apply SBS 2003 CAL's? SBS 2000 CAL's
will not work. Also did you check to see if the Licensing service is started
or stopped when your W2k server freezes?
"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 |
|
| |
External
Since: May 30, 2006
Posts: 144
|
(Msg. 5) Posted: Wed Jun 07, 2006 12:02 pm
Post subject: Re: SBS 2003 and member server W2000 problems [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
When you upgraded to SBS 2003 you did apply SBS 2003 CAL's? SBS 2000 CAL's
will not work. Also did you check to see if the Licensing service is started
or stopped when your W2k server freezes?
"Stephanie W" <StephanieW RemoveThis @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 |
|
| |
External
Since: Jun 07, 2006
Posts: 6
|
(Msg. 6) Posted: Wed Jun 07, 2006 8:22 pm
Post subject: Re: SBS 2003 and member server W2000 problems [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
We applied SBS2003 CALS to the workstations, but not to the W2000 member
server. Since this is a standalone server, I was under the impression that
it did not need a SBS CAL. It did not need a SBS2000 CAL. The license
logging service is running on both the SBS2003 server and the W2000 Server.
"MS User2006" wrote:
> When you upgraded to SBS 2003 you did apply SBS 2003 CAL's? SBS 2000 CAL's
> will not work. Also did you check to see if the Licensing service is started
> or stopped when your W2k server freezes?
>
> "Stephanie W" <StephanieW RemoveThis @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 |
|
| |
External
Since: Aug 13, 2005
Posts: 597
|
(Msg. 7) Posted: Wed Jun 07, 2006 8:55 pm
Post subject: Re: SBS 2003 and member server W2000 problems [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
Check your DNS on both servers. You are correct that the member server does
not need an SBS 2003 CAL.
Install the Windows Support Tools on both servers and run dcdiag and
netdiag.
Gregg Hill
"Stephanie W" <StephanieW DeleteThis @discussions.microsoft.com> wrote in message
news:8A2EF92D-243F-4583-88F6-86D08EFB202B@microsoft.com...
> We applied SBS2003 CALS to the workstations, but not to the W2000 member
> server. Since this is a standalone server, I was under the impression
> that
> it did not need a SBS CAL. It did not need a SBS2000 CAL. The license
> logging service is running on both the SBS2003 server and the W2000
> Server.
>
> "MS User2006" wrote:
>
>> When you upgraded to SBS 2003 you did apply SBS 2003 CAL's? SBS 2000
>> CAL's
>> will not work. Also did you check to see if the Licensing service is
>> started
>> or stopped when your W2k server freezes?
>>
>> "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 |
|
| |
External
Since: Aug 13, 2005
Posts: 597
|
(Msg. 8) Posted: Wed Jun 07, 2006 8:55 pm
Post subject: Re: SBS 2003 and member server W2000 problems [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
Check your DNS on both servers. You are correct that the member server does
not need an SBS 2003 CAL.
Install the Windows Support Tools on both servers and run dcdiag and
netdiag.
Gregg Hill
"Stephanie W" <StephanieW.TakeThisOut@discussions.microsoft.com> wrote in message
news:8A2EF92D-243F-4583-88F6-86D08EFB202B@microsoft.com...
> We applied SBS2003 CALS to the workstations, but not to the W2000 member
> server. Since this is a standalone server, I was under the impression
> that
> it did not need a SBS CAL. It did not need a SBS2000 CAL. The license
> logging service is running on both the SBS2003 server and the W2000
> Server.
>
> "MS User2006" wrote:
>
>> When you upgraded to SBS 2003 you did apply SBS 2003 CAL's? SBS 2000
>> CAL's
>> will not work. Also did you check to see if the Licensing service is
>> started
>> or stopped when your W2k server freezes?
>>
>> "Stephanie W" <StephanieW.TakeThisOut@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 |
|
| |
External
Since: Mar 04, 2004
Posts: 76
|
(Msg. 9) Posted: Wed Jun 07, 2006 10:20 pm
Post subject: Re: SBS 2003 and member server W2000 problems [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
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.RemoveThis@SBSmigration.com
"Stephanie W" <StephanieW.RemoveThis@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.RemoveThis@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 |
|
| |
External
Since: Mar 04, 2004
Posts: 76
|
(Msg. 10) Posted: Wed Jun 07, 2006 10:20 pm
Post subject: Re: SBS 2003 and member server W2000 problems [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
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 |
|
| |
External
Since: May 30, 2006
Posts: 144
|
(Msg. 11) Posted: Thu Jun 08, 2006 9:01 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?)
|
|
|
OK firat of all how did you apply SBS 2003 server CAL's to the workstation?
That is not possible and absolutely not necessary. Secondly your correct in
that you do not need CAL's for member servers in an SBS domain. However
given the fact that you do use SBS and that the SBS server is and always the
primary and licensed server you do need user or device CAL's for the SBS
server and SBS 2000 CAL's cannot be applied to a SBS 2003 server so when you
upgraded your OS you needed to upgrade your CAL's.
What did you do for licensing on the SBS 2000 server?
"Stephanie W" <StephanieW RemoveThis @discussions.microsoft.com> wrote in message
news:8A2EF92D-243F-4583-88F6-86D08EFB202B@microsoft.com...
> We applied SBS2003 CALS to the workstations, but not to the W2000 member
> server. Since this is a standalone server, I was under the impression
> that
> it did not need a SBS CAL. It did not need a SBS2000 CAL. The license
> logging service is running on both the SBS2003 server and the W2000
> Server.
>
> "MS User2006" wrote:
>
>> When you upgraded to SBS 2003 you did apply SBS 2003 CAL's? SBS 2000
>> CAL's
>> will not work. Also did you check to see if the Licensing service is
>> started
>> or stopped when your W2k server freezes?
>>
>> "Stephanie W" <StephanieW RemoveThis @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 |
|
| |
External
Since: Jun 07, 2006
Posts: 6
|
(Msg. 12) Posted: Thu Jun 08, 2006 9:25 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?)
|
|
|
No, it is connected to a SCSI Perc3 Raid5 controller.
"Jeff Middleton [SBS-MVP]" wrote:
> 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 |
|
| |
External
Since: Jun 07, 2006
Posts: 6
|
(Msg. 13) Posted: Thu Jun 08, 2006 9:25 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?)
|
|
|
Thankyou, I will try that.
"Gregg Hill" wrote:
> Check your DNS on both servers. You are correct that the member server does
> not need an SBS 2003 CAL.
>
> Install the Windows Support Tools on both servers and run dcdiag and
> netdiag.
>
> Gregg Hill
>
>
>
> "Stephanie W" <StephanieW RemoveThis @discussions.microsoft.com> wrote in message
> news:8A2EF92D-243F-4583-88F6-86D08EFB202B@microsoft.com...
> > We applied SBS2003 CALS to the workstations, but not to the W2000 member
> > server. Since this is a standalone server, I was under the impression
> > that
> > it did not need a SBS CAL. It did not need a SBS2000 CAL. The license
> > logging service is running on both the SBS2003 server and the W2000
> > Server.
> >
> > "MS User2006" wrote:
> >
> >> When you upgraded to SBS 2003 you did apply SBS 2003 CAL's? SBS 2000
> >> CAL's
> >> will not work. Also did you check to see if the Licensing service is
> >> started
> >> or stopped when your W2k server freezes?
> >>
> >> "Stephanie W" <StephanieW RemoveThis @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 |
|
| |
External
Since: Jun 07, 2006
Posts: 6
|
(Msg. 14) Posted: Thu Jun 08, 2006 9:29 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?)
|
|
|
When we purchased the SBS2003 upgrade, we also purchased the appropriate CAL
upgrades. In fact, if we did not, the SBS would limit us to the number of
workstations we could join to the domain. We did not "apply the CAL's"
directly to the workstations, sorry if I misled you. We were also properly
licensed for SBS2000.
Thanks
"MS User2006" wrote:
> OK firat of all how did you apply SBS 2003 server CAL's to the workstation?
> That is not possible and absolutely not necessary. Secondly your correct in
> that you do not need CAL's for member servers in an SBS domain. However
> given the fact that you do use SBS and that the SBS server is and always the
> primary and licensed server you do need user or device CAL's for the SBS
> server and SBS 2000 CAL's cannot be applied to a SBS 2003 server so when you
> upgraded your OS you needed to upgrade your CAL's.
> What did you do for licensing on the SBS 2000 server?
>
> "Stephanie W" <StephanieW RemoveThis @discussions.microsoft.com> wrote in message
> news:8A2EF92D-243F-4583-88F6-86D08EFB202B@microsoft.com...
> > We applied SBS2003 CALS to the workstations, but not to the W2000 member
> > server. Since this is a standalone server, I was under the impression
> > that
> > it did not need a SBS CAL. It did not need a SBS2000 CAL. The license
> > logging service is running on both the SBS2003 server and the W2000
> > Server.
> >
> > "MS User2006" wrote:
> >
> >> When you upgraded to SBS 2003 you did apply SBS 2003 CAL's? SBS 2000
> >> CAL's
> >> will not work. Also did you check to see if the Licensing service is
> >> started
> >> or stopped when your W2k server freezes?
> >>
> >> "Stephanie W" <StephanieW RemoveThis @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 |
|
| |
|
Les Connor [SBS Community
|
External
Since: May 29, 2006
Posts: 1208
|
(Msg. 15) Posted: Thu Jun 08, 2006 6:26 pm
Post subject: Re: SBS 2003 and member server W2000 problems [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
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 RemoveThis @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 RemoveThis @SBSmigration.com
>
>
> "Stephanie W" <StephanieW RemoveThis @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 RemoveThis @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 |
|
| |
FAQ
Profile
Private Messages
Log in
