Running fP on a Windows Server

Richard Hane yoresoft at sbcglobal.net
Wed Feb 27 09:34:50 PST 2008


Sorry *** Top Posted ****
   
  Don,
   
  We are retiring an old server (Win 2000) and moving fp this week to one of our other 4 servers runninng Win 2003.  Have you run in to any other issues?  One thing I am a little concerned about is that the server we are moving fp to has a Raid 1 on the 1st drive and a Raid 5 on the other 4 drives.
   
  I never had problems with fpODBC (1.0.13) running on the Win servers but I also have not had them on the Raid.
   
  Thank you,
  Rick Hane
  Controller
  DeLuxe Stitcher Company
  www.deluxestitcher.com
   
  

Don Coleman <dcoleman at dgcreact.com> wrote:
  > -----Original Message-----
> From: Nancy Palmquist [mailto:nlp at vss3.com]
> Sent: Tuesday, February 26, 2008 3:45 PM
> To: Don Coleman
> Subject: Re: Running fP on a Windows Server
> 
> Don Coleman wrote:
> > A client installed a new Windows Server 2003 yesterday. Their fP
> > application is run from a .BAT file found on the mapped network drive F
> to
> > their previous server. The new server is configured the same way and
> the fP
> > folder plus the .BAT file on the server was copied across the network
> from
> > the old to new server. Both clients are mapped the same way using the
> same
> > drive letter (I'm told, I'm not on site) and both clients were joined to
> the
> > same domain (a new domain name). There are two clients on this network
> who
> > access the fP application. The first client is working fine by
> accessing
> > the start-up batch file F:\REACT\REACT.BAT. However, when the second
> > client accesses the same start-up batch file the menus display but
> without
> > the normal color scheme found on client #1 (B/W only). Seemingly, the
> > config file is not being read on client #2. However, the config file is
> > there, visible from both clients mapped network drive. Client #2 is
> also
> > unable to access any of the fP files. When they press any menu
> selection
> > nothing happens. Since this is running from the same server and I have
> not
> > had them set-up any desktop shortcuts yet to eliminate any possible
> > differences there. (I had them delete the previous shortcut icons).
> > Running fP v5.0.05RN9.
> >
> > I'm confused and can't see what could be causing this behavior. Any
> ideas?
> >
> > Don Coleman
> > Donald G. Coleman, Consultant
> > 402 Andrew Circle
> > Indiana, PA 15701
> > dcoleman at dgcreact.com
> > (724) 349-6302
> >
> > _______________________________________________
> > Filepro-list mailing list
> > Filepro-list at lists.celestial.com
> > http://mailman.celestial.com/mailman/listinfo/filepro-list
> >
> >
> Don,


> My guess is that the PFDSK variable is not right.
> 
> set PFPROG=f:
> set PFDATA=f:
> set PFDIR=
> set PFDSK=f
> 
> These should cause the PFCONFIG to be equal to f:\fp\lib\config
> 
> When sharing the drive did they allow users to change data?
> 
> You may need to make users on the server to allow access. You have set
> this up
> with higher security than a normal peer-to-peer.
> 
> Put the following right before the p line in the bat file.
> 
> 
> set
> pause
> %pfprog%\fp\p
> 
> Then stop and look at what it shows.
> 
> I also put a file in the f: folder with a name you can spot to make sure
> the
> mapping is right.
> 
> For example, make a file called: "NEWDRIVEF.txt"
> 
> Then check to see if it is there.
> 
> Nancy
> 
> 
> 
> 
> 
> --
> Nancy Palmquist MOS & filePro Training Available
> Virtual Software Systems Web Based Training and Consulting
> PHONE: (412) 835-9417 Web site: http://www.vss3.com

Nancy:

The PFDSK variable was properly set in the .BAT file. What I didn't realize
was fP had been installed locally on both machines. We deleted the fP
folder on the one machine to make sure it wasn't looking at that
installation. That's when we lost the colors, etc. Your suggestion to use
the set command listed the problem. %PFPROG% was set to the local C drive
in the .BAT file. Since fP had previously been installed on both machines,
then removed from one, I know new why it would work on one, but not the
other. Setting PFPROG=F:\ took care of it. Thanks again,


Don Coleman
Donald G. Coleman, Consultant
402 Andrew Circle
Indiana, PA 15701
dcoleman at dgcreact.com
(724) 349-6302

_______________________________________________
Filepro-list mailing list
Filepro-list at lists.celestial.com
http://mailman.celestial.com/mailman/listinfo/filepro-list

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.celestial.com/pipermail/filepro-list/attachments/20080227/da53b5e6/attachment.html 


More information about the Filepro-list mailing list