User Support Forum

Hi,

I'm migrating the church server from 2003 to 2008 R2. Having trouble locating the PowerChurch v10 CD to install on the new server. I know I can download the maintenance releases. What about the original software?

It seems to run fine across the network (share name was also migrated). But don't I need/want to do a server install?

Thanks,

Mark Berry

pbumc wrote:Hi,

I'm migrating the church server from 2003 to 2008 R2. Having trouble locating the PowerChurch v10 CD to install on the new server. I know I can download the maintenance releases. What about the original software?

It seems to run fine across the network (share name was also migrated). But don't I need/want to do a server install?

Thanks,

Mark Berry

If you did a true migration, you should not need to reinstall Powerchurch unless a user trying to access the program on the Server itself is having a problem.

That said, you cannot download the v10/10.4 program, you can order a replacement CD from here:
https://www.powerchurch.com/catalog/index.php
for $15.00.

Thanks. The PowerChurch client installer is in the PowerChurch folder, so I assume I could install the client on the server if I needed to access PowerChurch on the server. If all the server install does is copy files, then maybe I don't need it.

Mark Berry

pbumc wrote:Thanks. The PowerChurch client installer is in the PowerChurch folder, so I assume I could install the client on the server if I needed to access PowerChurch on the server. If all the server install does is copy files, then maybe I don't need it.

Mark Berry

There is only one install program for the entire program, it installs all the executables, form & label templates, and basic data files on the 'server'. The Client install (NetSetup10.exe) for version 10 merely installs some runtimes, the main program runs off the server using the mapped server drive.

In other words, you really can't use that program to install the program. You said you migrated to Windows Server 2008, I'm assuming that you installed over the old W.S. 2003 ??

This usually maintains the shortcuts and their properties, so I'm wondering, do you have an exact error message you're seeing ??

Thanks for your thoughts.

I migrated from 32-bit Server 2003 to 64-bit Server 2008 R2. There is no upgrade path from 32-bit to 64-bit, so a migration means installing the new server OS from scratch on a second server, migrating Active Directory, copying data files (including NTFS Access Control Lists), and re-installing all programs. Hence my hunt for the PowerChrurch CD. My plan was to install it to the same path and the re-apply the latest maintenance release.

PowerChurch seems to run fine from a Windows desktop that accesses the shared directory on the new server.

You say the install program "installs all the executables, form & label templates, and basic data files." If by "install" you mean "copies all these files to a single folder on the server," then my data migration should have taken care of it. Most installers also update the registry and register components, often in %windir%\system32. If that is needed, then I'll need to re-run the server install.

Mark Berry

pbumc wrote:Thanks for your thoughts.

I migrated from 32-bit Server 2003 to 64-bit Server 2008 R2. There is no upgrade path from 32-bit to 64-bit, so a migration means installing the new server OS from scratch on a second server, migrating Active Directory, copying data files (including NTFS Access Control Lists), and re-installing all programs. Hence my hunt for the PowerChrurch CD. My plan was to install it to the same path and the re-apply the latest maintenance release.

PowerChurch seems to run fine from a Windows desktop that accesses the shared directory on the new server.

You say the install program "installs all the executables, form & label templates, and basic data files." If by "install" you mean "copies all these files to a single folder on the server," then my data migration should have taken care of it. Most installers also update the registry and register components, often in %windir%\system32. If that is needed, then I'll need to re-run the server install.

Mark Berry

Going from 32 bit to 64 bit does put a crimp in the issue. I wouldn't call that a migration, I'd just call it a operating system change !!

The install program doesn't just copy files 'into one directory', it also installs the FoxPro runtimes into the Microsoft Shared directories, and does the proper registry entries, which is probably why its not running on the server, as there are no registry entries on the upgraded server. You can try running the NetSetup10.exe program on the server, it may install the entries.

However, spending $15 on a replacement CD is cheap insurance to keep this from happening again in the future.

I don't really need to run PowerChurch on the server, though if I did, as you say, I could probably run netsetup10.exe.

Nonetheless, if the secretary can't locate the CD tomorrow I'll probably order a replacement--and make a backup!

Mark Berry

If you run the netsetup10 on the new server after copying the whole folder over. That should do everything you need without needing the version 10 installation CD.

Jeff wrote:If you run the netsetup10 on the new server after copying the whole folder over. That should do everything you need without needing the version 10 installation CD.

Thanks Jeff ... I had a feeling, but I didn't want to be definite. That said, could you use the version 11 NetSetup in the same way ??

I would have to check older versions, but yes, if you move the folder to a new computer and then run netsetupXX, it will install the necessary run-time files. In fact the installer now just copies the netsetup11 to the destination folder and then runs the netsetup11 silently to install the run-times. This way we don't duplicate any logic of where things need to be installed.

And (back on V10), if we don't need to run PowerChurch on the server, we don't even need to run netsetup10.exe on the server?

In other words, this is not client-server, where a server has to be set up and "listening" for client connections? It all just works through shared access to the one server folder?

Thanks,

That's correct.