Hello to everybody

I have developed a program thas was working very well in a windows 2000
server. This last month we decided to buy a new server but this one has a
windows small bussines server 2003 . When I try to execute this program with
this system nothing happens , no execution, no window opened, absolutely
nothing.
I also have some problems accesing the datafiles (DBF files). When accesing
a file, W2000 needs 1,5 seconds, WSBS2003 needs 35 seconds.
This is the code

   (AreaConc)->( DBGoTop() )
   Do While !(AreaConc)->( EOF() )
      AADD(aCompOld, {(AreaConc)->Num_Comp ,
(AreaConc)->P_Peso,(AreaConc)->Lab,(AreaConc)->Fase2})
      (AreaConc)->( DBSkip() )
   EndDo

Very simple

Does anybody have an idea why?
Thanks

Ernesto,

I assume you are trying to run the Xbase++ on the server and the DBF are on 
the same server.

Things to check:

XPPFatal.log generated?
Windows Event Logs report any problems?
Application has same environment as client workstation where it does run? 
(i.e. drive mappings)
Local security policy to restrictive to run the program? (Win2003 defaults 
to tighter security at console sessions than Win2000)
Any chance hardware/software DEP is the culprit?

I assume since you cannot run on the server, the performance problems are at 
a network workstation.

Things to check:

Is it truly taking 35 seconds in the loop or is it possible that the time is 
in opening the table?  If it is in establishing table access, do you have 
routing or name resolution configuration errors?
Any chance you forgot to disable oplocking when changing or upgrading to the 
Win2003?
Is the SBS server also an internet firewall/gateway using ISA 2000?  If so, 
have you made sure windows file services are disabled on the public nic, 
that the private nic is primary, and name resolution services (DNS/WINS) for 
the windows client are not resolving to the public nic.
No confusion regarding NetBui, TCP/IP, and NetBios encapsulated in TCP/IP?

I can confirm that Xbase++ apps run fine for me on Win2K3 and have also 
worked with 2K3 SBS, but I also use ADS which eliminates any direct file 
access of tables.  When properly configured, Win2K3 will perform at least as 
well as Win2K.  Win2K3 SBS (premium) is just a bundling of Win2K3, Exchange, 
Sql Server, and ISA with some minor extra features and scripts to simplify 
the installation.  Buying Win2K3, Exchange, Sql Server and ISA seperately 
and installing on single computer is esentially same as SBS except more work 
and more expensive.

Hopefully something above points you to a solution.

Rodd

"Ernesto Avedillo" <eavedillo@iacsl.e.telefonica.net> wrote in message 
news:4ace1b5d$1211a25a$9c5a1@news.alaska-software.com...
> Hello to everybody
>
> I have developed a program thas was working very well in a windows 2000
> server. This last month we decided to buy a new server but this one has a
> windows small bussines server 2003 . When I try to execute this program 
> with
> this system nothing happens , no execution, no window opened, absolutely
> nothing.
> I also have some problems accesing the datafiles (DBF files). When 
> accesing
> a file, W2000 needs 1,5 seconds, WSBS2003 needs 35 seconds.
> This is the code
>
>   (AreaConc)->( DBGoTop() )
>   Do While !(AreaConc)->( EOF() )
>      AADD(aCompOld, {(AreaConc)->Num_Comp ,
> (AreaConc)->P_Peso,(AreaConc)->Lab,(AreaConc)->Fase2})
>      (AreaConc)->( DBSkip() )
>   EndDo
>
> Very simple
>
> Does anybody have an idea why?
> Thanks
>
>
>
>
>

Hi Rodd,
I'm having nearly the same problem. My programm works perfektly on W2k
Server but on a very fast W2k3 server with 2GB memory it takes 3 minutes to
built the NTX-Files (50 sec. before). The files and the programm is in the
same directory on the server. I heard, that there are problems with other
DB-Systems too like FoxPro

Volker

"Rodd Graham" <rodd@grahamautomation.com> schrieb im Newsbeitrag
news:410eac7a$1ecc100c$9d073@news.alaska-software.com...
> Ernesto,
>
> I assume you are trying to run the Xbase++ on the server and the DBF are
on
> the same server.
>
> Things to check:
>
> XPPFatal.log generated?
> Windows Event Logs report any problems?
> Application has same environment as client workstation where it does run?
> (i.e. drive mappings)
> Local security policy to restrictive to run the program? (Win2003 defaults
> to tighter security at console sessions than Win2000)
> Any chance hardware/software DEP is the culprit?
>
> I assume since you cannot run on the server, the performance problems are
at
> a network workstation.
>
> Things to check:
>
> Is it truly taking 35 seconds in the loop or is it possible that the time
is
> in opening the table?  If it is in establishing table access, do you have
> routing or name resolution configuration errors?
> Any chance you forgot to disable oplocking when changing or upgrading to
the
> Win2003?
> Is the SBS server also an internet firewall/gateway using ISA 2000?  If
so,
> have you made sure windows file services are disabled on the public nic,
> that the private nic is primary, and name resolution services (DNS/WINS)
for
> the windows client are not resolving to the public nic.
> No confusion regarding NetBui, TCP/IP, and NetBios encapsulated in TCP/IP?
>
> I can confirm that Xbase++ apps run fine for me on Win2K3 and have also
> worked with 2K3 SBS, but I also use ADS which eliminates any direct file
> access of tables.  When properly configured, Win2K3 will perform at least
as
> well as Win2K.  Win2K3 SBS (premium) is just a bundling of Win2K3,
Exchange,
> Sql Server, and ISA with some minor extra features and scripts to simplify
> the installation.  Buying Win2K3, Exchange, Sql Server and ISA seperately
> and installing on single computer is esentially same as SBS except more
work
> and more expensive.
>
> Hopefully something above points you to a solution.
>
> Rodd
>
> "Ernesto Avedillo" <eavedillo@iacsl.e.telefonica.net> wrote in message
> news:4ace1b5d$1211a25a$9c5a1@news.alaska-software.com...
> > Hello to everybody
> >
> > I have developed a program thas was working very well in a windows 2000
> > server. This last month we decided to buy a new server but this one has
a
> > windows small bussines server 2003 . When I try to execute this program
> > with
> > this system nothing happens , no execution, no window opened, absolutely
> > nothing.
> > I also have some problems accesing the datafiles (DBF files). When
> > accesing
> > a file, W2000 needs 1,5 seconds, WSBS2003 needs 35 seconds.
> > This is the code
> >
> >   (AreaConc)->( DBGoTop() )
> >   Do While !(AreaConc)->( EOF() )
> >      AADD(aCompOld, {(AreaConc)->Num_Comp ,
> > (AreaConc)->P_Peso,(AreaConc)->Lab,(AreaConc)->Fase2})
> >      (AreaConc)->( DBSkip() )
> >   EndDo
> >
> > Very simple
> >
> > Does anybody have an idea why?
> > Thanks
> >
> >
> >
> >
> >
>
>

Hi Rodd,
I'm having nearly the same problem. My programm works perfektly on W2k
Server but on a very fast W2k3 server with 2GB memory it takes 3 minutes to
built the NTX-Files (50 sec. before). The files and the programm is in the
same directory on the server. I heard, that there are problems with other
DB-Systems too like FoxPro

Volker
"Rodd Graham" <rodd@grahamautomation.com> schrieb im Newsbeitrag
news:410eac7a$1ecc100c$9d073@news.alaska-software.com...
> Ernesto,
>
> I assume you are trying to run the Xbase++ on the server and the DBF are
on
> the same server.
>
> Things to check:
>
> XPPFatal.log generated?
> Windows Event Logs report any problems?
> Application has same environment as client workstation where it does run?
> (i.e. drive mappings)
> Local security policy to restrictive to run the program? (Win2003 defaults
> to tighter security at console sessions than Win2000)
> Any chance hardware/software DEP is the culprit?
>
> I assume since you cannot run on the server, the performance problems are
at
> a network workstation.
>
> Things to check:
>
> Is it truly taking 35 seconds in the loop or is it possible that the time
is
> in opening the table?  If it is in establishing table access, do you have
> routing or name resolution configuration errors?
> Any chance you forgot to disable oplocking when changing or upgrading to
the
> Win2003?
> Is the SBS server also an internet firewall/gateway using ISA 2000?  If
so,
> have you made sure windows file services are disabled on the public nic,
> that the private nic is primary, and name resolution services (DNS/WINS)
for
> the windows client are not resolving to the public nic.
> No confusion regarding NetBui, TCP/IP, and NetBios encapsulated in TCP/IP?
>
> I can confirm that Xbase++ apps run fine for me on Win2K3 and have also
> worked with 2K3 SBS, but I also use ADS which eliminates any direct file
> access of tables.  When properly configured, Win2K3 will perform at least
as
> well as Win2K.  Win2K3 SBS (premium) is just a bundling of Win2K3,
Exchange,
> Sql Server, and ISA with some minor extra features and scripts to simplify
> the installation.  Buying Win2K3, Exchange, Sql Server and ISA seperately
> and installing on single computer is esentially same as SBS except more
work
> and more expensive.
>
> Hopefully something above points you to a solution.
>
> Rodd
>
> "Ernesto Avedillo" <eavedillo@iacsl.e.telefonica.net> wrote in message
> news:4ace1b5d$1211a25a$9c5a1@news.alaska-software.com...
> > Hello to everybody
> >
> > I have developed a program thas was working very well in a windows 2000
> > server. This last month we decided to buy a new server but this one has
a
> > windows small bussines server 2003 . When I try to execute this program
> > with
> > this system nothing happens , no execution, no window opened, absolutely
> > nothing.
> > I also have some problems accesing the datafiles (DBF files). When
> > accesing
> > a file, W2000 needs 1,5 seconds, WSBS2003 needs 35 seconds.
> > This is the code
> >
> >   (AreaConc)->( DBGoTop() )
> >   Do While !(AreaConc)->( EOF() )
> >      AADD(aCompOld, {(AreaConc)->Num_Comp ,
> > (AreaConc)->P_Peso,(AreaConc)->Lab,(AreaConc)->Fase2})
> >      (AreaConc)->( DBSkip() )
> >   EndDo
> >
> > Very simple
> >
> > Does anybody have an idea why?
> > Thanks
> >
> >
> >
> >
> >
>
>

This is just M$ trying to get you to buy MSSQL. Has all the Caching been 
tuned off??

Jim

Volker Thimm wrote:
> Hi Rodd,
> I'm having nearly the same problem. My programm works perfektly on W2k
> Server but on a very fast W2k3 server with 2GB memory it takes 3 minutes to
> built the NTX-Files (50 sec. before). The files and the programm is in the
> same directory on the server. I heard, that there are problems with other
> DB-Systems too like FoxPro
> 
> Volker
> "Rodd Graham" <rodd@grahamautomation.com> schrieb im Newsbeitrag
> news:410eac7a$1ecc100c$9d073@news.alaska-software.com...
> 
>>Ernesto,
>>
>>I assume you are trying to run the Xbase++ on the server and the DBF are
> 
> on
> 
>>the same server.
>>
>>Things to check:
>>
>>XPPFatal.log generated?
>>Windows Event Logs report any problems?
>>Application has same environment as client workstation where it does run?
>>(i.e. drive mappings)
>>Local security policy to restrictive to run the program? (Win2003 defaults
>>to tighter security at console sessions than Win2000)
>>Any chance hardware/software DEP is the culprit?
>>
>>I assume since you cannot run on the server, the performance problems are
> 
> at
> 
>>a network workstation.
>>
>>Things to check:
>>
>>Is it truly taking 35 seconds in the loop or is it possible that the time
> 
> is
> 
>>in opening the table?  If it is in establishing table access, do you have
>>routing or name resolution configuration errors?
>>Any chance you forgot to disable oplocking when changing or upgrading to
> 
> the
> 
>>Win2003?
>>Is the SBS server also an internet firewall/gateway using ISA 2000?  If
> 
> so,
> 
>>have you made sure windows file services are disabled on the public nic,
>>that the private nic is primary, and name resolution services (DNS/WINS)
> 
> for
> 
>>the windows client are not resolving to the public nic.
>>No confusion regarding NetBui, TCP/IP, and NetBios encapsulated in TCP/IP?
>>
>>I can confirm that Xbase++ apps run fine for me on Win2K3 and have also
>>worked with 2K3 SBS, but I also use ADS which eliminates any direct file
>>access of tables.  When properly configured, Win2K3 will perform at least
> 
> as
> 
>>well as Win2K.  Win2K3 SBS (premium) is just a bundling of Win2K3,
> 
> Exchange,
> 
>>Sql Server, and ISA with some minor extra features and scripts to simplify
>>the installation.  Buying Win2K3, Exchange, Sql Server and ISA seperately
>>and installing on single computer is esentially same as SBS except more
> 
> work
> 
>>and more expensive.
>>
>>Hopefully something above points you to a solution.
>>
>>Rodd
>>
>>"Ernesto Avedillo" <eavedillo@iacsl.e.telefonica.net> wrote in message
>>news:4ace1b5d$1211a25a$9c5a1@news.alaska-software.com...
>>
>>>Hello to everybody
>>>
>>>I have developed a program thas was working very well in a windows 2000
>>>server. This last month we decided to buy a new server but this one has
> 
> a
> 
>>>windows small bussines server 2003 . When I try to execute this program
>>>with
>>>this system nothing happens , no execution, no window opened, absolutely
>>>nothing.
>>>I also have some problems accesing the datafiles (DBF files). When
>>>accesing
>>>a file, W2000 needs 1,5 seconds, WSBS2003 needs 35 seconds.
>>>This is the code
>>>
>>>  (AreaConc)->( DBGoTop() )
>>>  Do While !(AreaConc)->( EOF() )
>>>     AADD(aCompOld, {(AreaConc)->Num_Comp ,
>>>(AreaConc)->P_Peso,(AreaConc)->Lab,(AreaConc)->Fase2})
>>>     (AreaConc)->( DBSkip() )
>>>  EndDo
>>>
>>>Very simple
>>>
>>>Does anybody have an idea why?
>>>Thanks
>>>
>>>
>>>
>>>
>>>
>>
>>
> 
>