Crash in Personal Profiles

[MTZDetroit]

Running PC 11.1 ML 12/30/2013
Server running Windows Server 2008
Client running Windows 8.1 64 bit

We have multiple clients accessing Power Church throughout the day. Most of them running Windows XP, a few Windows 7.

Two users are running Windows 8.1 and regularly get crashes when updating Personal Profiles with the following message:
PROGRAM:resolve
LINE: 56
ERROR: 41
MESSAGE: Memo file\\ZIONSERVER\Power Church-Main Church\DATA\ma.FPT is missing or invalid

Seems to only occur in Windows 8.1 and when updating any Custom Field.

Power Church must be closed using Windows Task Manager. When started up again the data that was updated is there.

Help!

Thanks.

Michael Sanchez
PC Administrator
User 7+ years
Mt Zion Temple-Clarkston, MI

[NeilZ]

Running PC 11.1 ML 12/30/2013
Server running Windows Server 2008
Client running Windows 8.1 64 bit

We have multiple clients accessing Power Church throughout the day. Most of them running Windows XP, a few Windows 7.

Two users are running Windows 8.1 and regularly get crashes when updating Personal Profiles with the following message:
PROGRAM:resolve
LINE: 56
ERROR: 41
MESSAGE: Memo file\\ZIONSERVER\Power Church-Main Church\DATA\ma.FPT is missing or invalid

Seems to only occur in Windows 8.1 and when updating any Custom Field.

Power Church must be closed using Windows Task Manager. When started up again the data that was updated is there.

Help!

Thanks.

Michael Sanchez
PC Administrator
User 7+ years
Mt Zion Temple-Clarkston, MI

Just wondering ... did you map the Powerchurch directory to a letter on the servers? It doesn't appear so ..

[MTZDetroit]

Neil, thanks for the reply.

Yes, I have mapped the drive to the server. That got me thinking from where I initially installed the Power Church client.

So, I used Revo Uninstaller to remove all instances of the runtime files from my hard drive as well as scrub the registry for any links to Power Church.

I then went to the mapped drive for Power Church and ran NetSetup11 directly from that drive.

So far so good. The odd thing is we have never had this issue with any other OS until Windows 8. And almost all of the machines that I have installed the client for Power Church the drive is NOT mapped. We have the runtime client installed on about 20 pc's.

Thanks for the tip. We'll see if it holds up. So far I have not been able to recreate the crash.

[NeilZ]

Neil, thanks for the reply.

Yes, I have mapped the drive to the server. That got me thinking from where I initially installed the Power Church client.

So, I used Revo Uninstaller to remove all instances of the runtime files from my hard drive as well as scrub the registry for any links to Power Church.

I then went to the mapped drive for Power Church and ran NetSetup11 directly from that drive.

So far so good. The odd thing is we have never had this issue with any other OS until Windows 8. And almost all of the machines that I have installed the client for Power Church the drive is NOT mapped. We have the runtime client installed on about 20 pc's.

Thanks for the tip. We'll see if it holds up. So far I have not been able to recreate the crash.

FWIW ... Powerchurch strongly recommends that each client have the c:\powerchurch\pcplusxxx directory mapped to their computer. It will work as you have it, but over the years, I've seen more issues with non-mapped clients than with mapped ones. YMMV !!

[Zorak]

Powerchurch strongly recommends that each client have the c:\powerchurch\ directory mapped to their computer.

Fixed it for you. haha Mapping to the root PowerChurch directory means that you won't have to change it each time you install a new version upgrade. Also, we have seen some weirdo permissions issues when the drive is mapped directly to the PCPLUSXX directoy.

[NeilZ]

Powerchurch strongly recommends that each client have the c:\powerchurch\ directory mapped to their computer.

Fixed it for you. haha Mapping to the root PowerChurch directory means that you won't have to change it each time you install a new version upgrade. Also, we have seen some weirdo permissions issues when the drive is mapped directly to the PCPLUSXX directoy.

Thanks ... forgot that