FilePro & Windows issues

Jason Garner jason.garner at evalsvs.com
Wed Jan 23 07:57:02 PST 2019


For the issues with connecting to the FPLM service, is this just on the
Windows 10 machines? We had an issue a while ago where on the Win10
machines, filepro would intermittently throw a "could not contact the
license manager error". Win7 machines were just fine."

The issue was a Windows 10 update that broke SMBv1 protocol. Microsoft does
not support SMBv1 anymore...but there are still enough people that are on
Server 2003 (running programs launched from mapped drives using the SMBv1
protocol) that complained to force Microsoft to roll out another patch to
fix the problem.

We have moved away from client-server and running FP over the network. But
when we did things this way, we always rolled the server back to only using
the SMBv1 protocol due to problems with Opportunistic Locking and
performance caching of later SMB protocols in a multi user environment.

I am not sure if you do the same thing. You mentioned RDP (remote desktop
from the clients to the FPserver and running fp programs locally?)...maybe
that is the way that you are doing it in which case make sure that your FP
Environment (PFDISK, PFDATA) is configured to use the local drive and not a
mapped drive.

Anyways the overall point is if you happen to be utilizing the SMBv1
protocol/network share this could be the cause of some of the weirdness as
Microsoft no longer supports it and is trying to do away with it entirely
because of security concerns.

I hope this helps.


On Wed, Jan 23, 2019 at 5:07 AM <filepro-list-request at lists.celestial.com>
wrote:

> Send Filepro-list mailing list submissions to
>         filepro-list at lists.celestial.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         http://mailman.celestial.com/mailman/listinfo/filepro-list
> or, via email, send a message with subject or body 'help' to
>         filepro-list-request at lists.celestial.com
>
> You can reach the person managing the list at
>         filepro-list-owner at lists.celestial.com
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Filepro-list digest..."
>
>
> Today's Topics:
>
>    1. FilePro & Windows issues (Richard Kreiss)
>    2. Re: FilePro & Windows issues (Bob Rasmussen)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 22 Jan 2019 22:27:30 +0000
> From: Richard Kreiss <rkreiss at gccconsulting.net>
> To: "'filepro-list at lists.celestial.com'"
>         <filepro-list at lists.celestial.com>
> Subject: FilePro & Windows issues
> Message-ID:
>         <
> DM6PR04MB4876423D07B20A9768046959B7980 at DM6PR04MB4876.namprd04.prod.outlook.com
> >
>
> Content-Type: text/plain; charset="us-ascii"
>
> I recently spent a lot of time trying to track down a problem one of my
> clients was having with filePro.  Server 2012 with workstations running
> both Windows 10 64 bit and Win 7 32 bit.
>
> The have been creating letters in a PDF format from IUA.  This has been
> working for about a year with no issues.  About 3 weeks ago they started to
> have a problem with the PDF output being too far to the right.  I copied
> the PDF output format to my system and then using filePro copied the format
> to a new name.  I then added tabs to control the spacing.  The new formats
> were uploaded and tested on their system.  As they are running both the 32
> and 64 bit version of filePro 5.8.03, I tested both using remote desktop
> (64 bit).  Everything appeared to work was I got no error messages.  This
> was not the case, the 32 bit version could not "find" the *.out file.  The
> 64 bit version had no issue.  I could access the letter format with no
> problem,  *clerk could not find it.  By the way, both versions of filePro
> created the PDFs on my system.
>
> The other issue I had was after installing 6.0.00 and the license service
> for 6.0.00 with their 6.0.00 license, the service would not start.  Access
> denied was the windows error message.  When I reinstalled the 5.8.03
> license service there was no problem with it starting.
>
> I was informed when this was going on that nothing had changed on their
> system.  Well something had changed, In the first case fplm print table was
> not being fully accessed and logos were not be loaded.  I was able to
> correct the logo issue but the small scissor graphic is not being printed.
>
> So, to conclude, something did change either through a system upgrade or
> manually.  As I have administrator rights on the system, I have to conclude
> that there is something else at work on their system causing this issue.
>
> I have suggested to the CEO that those employees who need to create the
> PDF letters use Remote desktop to access the program if they have a 32 bit
> OS. Remote Desktop logs into a 64 bit OS and therefore has no problem
> creading the PDFs.  As for why the Access Denied error when the service
> tries to access fplmservice.exe, I have no idea why this happened.
>
>
>
>
>
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: winmail.dat
> Type: application/ms-tnef
> Size: 15733 bytes
> Desc: not available
> URL: <
> http://mailman.celestial.com/pipermail/filepro-list/attachments/20190122/52beaa41/attachment.bin
> >
>
>
> ------------------------------
>
> Message: 2
> Date: Tue, 22 Jan 2019 14:46:16 -0800 (PST)
> From: Bob Rasmussen <ras at anzio.com>
> To: Richard Kreiss <rkreiss at gccconsulting.net>
> Cc: "'filepro-list at lists.celestial.com'"
>         <filepro-list at lists.celestial.com>
> Subject: Re: FilePro & Windows issues
> Message-ID: <alpine.DEB.2.10.1901221443070.17754 at server-04>
> Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
>
> Richard, by any chance are any of the configuration files anywhere under
> the "c:\Program files" or "C:\Program Files (x86)" folders? If so, Windows
> may be virtualizing their location, depending on a lot of factors.
>
> On Tue, 22 Jan 2019, Richard Kreiss via Filepro-list wrote:
>
> > I recently spent a lot of time trying to track down a problem one of my
> clients was having with filePro.  Server 2012 with workstations running
> both Windows 10 64 bit and Win 7 32 bit.
> >
> > The have been creating letters in a PDF format from IUA.  This has been
> working for about a year with no issues.  About 3 weeks ago they started to
> have a problem with the PDF output being too far to the right.  I copied
> the PDF output format to my system and then using filePro copied the format
> to a new name.  I then added tabs to control the spacing.  The new formats
> were uploaded and tested on their system.  As they are running both the 32
> and 64 bit version of filePro 5.8.03, I tested both using remote desktop
> (64 bit).  Everything appeared to work was I got no error messages.  This
> was not the case, the 32 bit version could not "find" the *.out file.  The
> 64 bit version had no issue.  I could access the letter format with no
> problem,  *clerk could not find it.  By the way, both versions of filePro
> created the PDFs on my system.
> >
> > The other issue I had was after installing 6.0.00 and the license
> service for 6.0.00 with their 6.0.00 license, the service would not start.
> Access denied was the windows error message.  When I reinstalled the 5.8.03
> license service there was no problem with it starting.
> >
> > I was informed when this was going on that nothing had changed on their
> system.  Well something had changed, In the first case fplm print table was
> not being fully accessed and logos were not be loaded.  I was able to
> correct the logo issue but the small scissor graphic is not being printed.
> >
> > So, to conclude, something did change either through a system upgrade or
> manually.  As I have administrator rights on the system, I have to conclude
> that there is something else at work on their system causing this issue.
> >
> > I have suggested to the CEO that those employees who need to create the
> PDF letters use Remote desktop to access the program if they have a 32 bit
> OS. Remote Desktop logs into a 64 bit OS and therefore has no problem
> creading the PDFs.  As for why the Access Denied error when the service
> tries to access fplmservice.exe, I have no idea why this happened.
> >
> >
> >
> >
> >
> > -------------- next part --------------
> > A non-text attachment was scrubbed...
> > Name: winmail.dat
> > Type: application/ms-tnef
> > Size: 15733 bytes
> > Desc: not available
> > URL: <
> http://mailman.celestial.com/pipermail/filepro-list/attachments/20190122/52beaa41/attachment.bin
> >
> > _______________________________________________
> > Filepro-list mailing list
> > Filepro-list at lists.celestial.com
> > Subscribe/Unsubscribe/Subscription Changes
> > http://mailman.celestial.com/mailman/listinfo/filepro-list
> >
>
> Regards,
> ....Bob Rasmussen,   President,   Rasmussen Software, Inc.
>
> personal e-mail: ras at anzio.com
>   company e-mail: rsi at anzio.com
>            voice: (US) 503-624-0360 (9:00-6:00 Pacific Time)
>              fax: (US) 503-624-0760
>              web: http://www.anzio.com
>   street address: Rasmussen Software, Inc.
>                   10240 SW Nimbus, Suite L9
>                   Portland, OR  97223  USA
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> http://mailman.celestial.com/mailman/listinfo/filepro-list
>
>
> ------------------------------
>
> End of Filepro-list Digest, Vol 180, Issue 8
> ********************************************
>


-- 
Jason Garner
Systems Administrator

1801 Oberlin Rd, Suite 204
Middletown, PA 17057
Work   717-985-1122 x 1139
Mobile 717-645-3521
<tim.barr at evalsvs.com>jason.garner at evalsvs.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.celestial.com/pipermail/filepro-list/attachments/20190123/a2404b9c/attachment.html>


More information about the Filepro-list mailing list