MAS200 Pervasive setup

My server went down when the C: drive ran out of disk space.  Although I was able to save the data on the D partition the C partition was history.  Because I replaced the hardware I am not able to use a system state restore.  It would appear that we stopped doing them anyway since the tape was not big enough to hold all our data and the system state.  So I slipstreamed a server 2000 disk with SP4 and recreated the C partition.  I need to get MAS200 running again but I don't know how to get Pervasive installed and configured.  The only thing I know for sure is that it was using port 10000.  The data is intact since it was on the D partition.  We also use the latest Peachtree which also uses the pervasive server.  I thought I could install the server portion first and the make the changes for MAS200.  That would get pervasive onto the server.
LVL 4
MikeKAtLCSAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
MikeKAtLCSConnect With a Mentor Author Commented:
There are threads that talk about moving MAS90 to another server.  The suggestions work.  The only problem I ran into was BackupExec and MAS200 both use port 10000.  It took a while to figure out that the conflict was causing communication errors.  Finally after a reboot and looking at the event logs I found an entry from BackuExec referring to one of its services not running due to a port 10000 conflict.  You can move the port to 9000 in the services file under windows\system32\drivers\etc on the server.  The port is used by the remote windows agent.  Instructions are on Symantecs web site.  I am using Backup Exec 10d.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.