<div>Sorry *** Top Posted ****</div> <div> </div> <div>Don,</div> <div> </div> <div>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.</div> <div> </div> <div>I never had problems with fpODBC (1.0.13) running on the Win servers but I also have not had them on the Raid.</div> <div> </div> <div>Thank you,</div> <div>Rick Hane</div> <div>Controller</div> <div>DeLuxe Stitcher Company</div> <div><A href="http://www.deluxestitcher.com">www.deluxestitcher.com</A></div> <div> </div> <div><BR><BR><B><I>Don Coleman <dcoleman@dgcreact.com></I></B> wrote:</div> <BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">> -----Original
Message-----<BR>> From: Nancy Palmquist [mailto:nlp@vss3.com]<BR>> Sent: Tuesday, February 26, 2008 3:45 PM<BR>> To: Don Coleman<BR>> Subject: Re: Running fP on a Windows Server<BR>> <BR>> Don Coleman wrote:<BR>> > A client installed a new Windows Server 2003 yesterday. Their fP<BR>> > application is run from a .BAT file found on the mapped network drive F<BR>> to<BR>> > their previous server. The new server is configured the same way and<BR>> the fP<BR>> > folder plus the .BAT file on the server was copied across the network<BR>> from<BR>> > the old to new server. Both clients are mapped the same way using the<BR>> same<BR>> > drive letter (I'm told, I'm not on site) and both clients were joined to<BR>> the<BR>> > same domain (a new domain name). There are two clients on this network<BR>> who<BR>> > access the fP application. The first client is working fine by<BR>> accessing<BR>>
> the start-up batch file F:\REACT\REACT.BAT. However, when the second<BR>> > client accesses the same start-up batch file the menus display but<BR>> without<BR>> > the normal color scheme found on client #1 (B/W only). Seemingly, the<BR>> > config file is not being read on client #2. However, the config file is<BR>> > there, visible from both clients mapped network drive. Client #2 is<BR>> also<BR>> > unable to access any of the fP files. When they press any menu<BR>> selection<BR>> > nothing happens. Since this is running from the same server and I have<BR>> not<BR>> > had them set-up any desktop shortcuts yet to eliminate any possible<BR>> > differences there. (I had them delete the previous shortcut icons).<BR>> > Running fP v5.0.05RN9.<BR>> ><BR>> > I'm confused and can't see what could be causing this behavior. Any<BR>> ideas?<BR>> ><BR>> > Don Coleman<BR>> > Donald
G. Coleman, Consultant<BR>> > 402 Andrew Circle<BR>> > Indiana, PA 15701<BR>> > dcoleman@dgcreact.com<BR>> > (724) 349-6302<BR>> ><BR>> > _______________________________________________<BR>> > Filepro-list mailing list<BR>> > Filepro-list@lists.celestial.com<BR>> > http://mailman.celestial.com/mailman/listinfo/filepro-list<BR>> ><BR>> ><BR>> Don,<BR><BR><BR>> My guess is that the PFDSK variable is not right.<BR>> <BR>> set PFPROG=f:<BR>> set PFDATA=f:<BR>> set PFDIR=<BR>> set PFDSK=f<BR>> <BR>> These should cause the PFCONFIG to be equal to f:\fp\lib\config<BR>> <BR>> When sharing the drive did they allow users to change data?<BR>> <BR>> You may need to make users on the server to allow access. You have set<BR>> this up<BR>> with higher security than a normal peer-to-peer.<BR>> <BR>> Put the following right before the p line in the bat file.<BR>> <BR>>
<BR>> set<BR>> pause<BR>> %pfprog%\fp\p<BR>> <BR>> Then stop and look at what it shows.<BR>> <BR>> I also put a file in the f: folder with a name you can spot to make sure<BR>> the<BR>> mapping is right.<BR>> <BR>> For example, make a file called: "NEWDRIVEF.txt"<BR>> <BR>> Then check to see if it is there.<BR>> <BR>> Nancy<BR>> <BR>> <BR>> <BR>> <BR>> <BR>> --<BR>> Nancy Palmquist MOS & filePro Training Available<BR>> Virtual Software Systems Web Based Training and Consulting<BR>> PHONE: (412) 835-9417 Web site: http://www.vss3.com<BR><BR>Nancy:<BR><BR>The PFDSK variable was properly set in the .BAT file. What I didn't realize<BR>was fP had been installed locally on both machines. We deleted the fP<BR>folder on the one machine to make sure it wasn't looking at that<BR>installation. That's when we lost the colors, etc. Your suggestion to use<BR>the set command listed the problem. %PFPROG% was set
to the local C drive<BR>in the .BAT file. Since fP had previously been installed on both machines,<BR>then removed from one, I know new why it would work on one, but not the<BR>other. Setting PFPROG=F:\ took care of it. Thanks again,<BR><BR><BR>Don Coleman<BR>Donald G. Coleman, Consultant<BR>402 Andrew Circle<BR>Indiana, PA 15701<BR>dcoleman@dgcreact.com<BR>(724) 349-6302<BR><BR>_______________________________________________<BR>Filepro-list mailing list<BR>Filepro-list@lists.celestial.com<BR>http://mailman.celestial.com/mailman/listinfo/filepro-list<BR></BLOCKQUOTE><BR>