That's an error in the installation of Epicor, not with that tool.
The fix is this:
Shut down all AppServers and databases and OpenEdge. Open Task Manager and
check for the Admsrvc any processes with a _ to start the name and any
Java.exe files that are running, these ALL need to be shut down before
continuing.
Go to the Epicor\oe102a\properties folder.
Find the file called conmgr.properties MAKE A COPY
Open conmgr.properties in notepad
Scroll down and you will see all the settings for the databases, this will
be the first one most likely with slightly different settings. This is the
correct one you will see.
[configuration.epicor905.defaultconfiguration]
asynchronouspagewriters=2
beforeimagebuffers=25
blocksindatabasebuffers=20000
database=epicor905
displayname=defaultConfiguration
internalcodepage=utf-8
locktableentries=204800
logcharacterset=utf-8
maxservers=43
maxusers=136
otherargs=
servergroups=epicor905.defaultconfiguration.odbcgroup,
epicor905.defaultconfiguration.mfgsysgroup
spinlockretries=50000
Then you can find the Pilot, test, and train ones after that one, this is
what your test one will look like.
[configuration.epicortest905.defaultconfiguration]
asynchronouspagewriters=2
blocksindatabasebuffers=20000
database=epicortest905
displayname=defaultConfiguration
internalcodepage=utf-8
locktableentries=204800
logcharacterset=utf-8
maxservers=43
maxusers=136
otherargs=
servergroups=epicortest905.defaultconfiguration.odbcgroup,
epicor905.defaultconfiguration.mfgsysgroup
spinlockretries=50000
You may already see the problem, you may not.
If you look at the servergroups line you will notice it is referencing the
mfgsysgroup from the Live/Production DB instead of for the test DB.
Manually edit that line to say:
servergroups=epicortest905.defaultconfiguration.odbcgroup,
epicortest905.defaultconfiguration.mfgsysgroup
Just type test into the line after the epicor and before the 905. Do not
type anything else anywhere else, do not adjust line spacing to make it look
better or anything else, this will most likely cause the file to become
corrupted.
Repeat as needed for the other databases.
Then save the file and start up the Admin Service again, make sure that all
DBs and appservers etc are still there when you open the OE Management
website, if not then the file was corrupted. In which case, go back and copy
the copy of the original you made and replace the one you just corrupted.
Repeat as necessary til you get it to work.
Ned
Alternative Technology Partners
-----Original Message-----
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
Doma Reddy
Sent: Wednesday, February 16, 2011 5:05 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Port Numbers Duplication in Open Edge Management
Explorer(Web Based tool to manage App Servers)
Did anybody find that in the New webbased Tool to manage App Servers "Open
Edge Management Explorer", if we change the Mfgsys pot number on one DB it
changes on all the DB's for some reason if you change the port number on
pilot, it changes to the same port number on Main DB, TestDB & Train DB.
Â
Any work around to resolve this.
Â
Thanks,
Doma.
[Non-text portions of this message have been removed]
------------------------------------
Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must have
already linked your email address to a yahoo id to enable access. )
(1) To access the Files Section of our Yahoo!Group for Report Builder and
Crystal Reports and other 'goodies', please goto:
http://groups.yahoo.com/group/vantage/files/.
(2) To search through old msg's goto:
http://groups.yahoo.com/group/vantage/messages
(3) To view links to Vendors that provide Vantage services goto:
http://groups.yahoo.com/group/vantage/linksYahoo! Groups Links
The fix is this:
Shut down all AppServers and databases and OpenEdge. Open Task Manager and
check for the Admsrvc any processes with a _ to start the name and any
Java.exe files that are running, these ALL need to be shut down before
continuing.
Go to the Epicor\oe102a\properties folder.
Find the file called conmgr.properties MAKE A COPY
Open conmgr.properties in notepad
Scroll down and you will see all the settings for the databases, this will
be the first one most likely with slightly different settings. This is the
correct one you will see.
[configuration.epicor905.defaultconfiguration]
asynchronouspagewriters=2
beforeimagebuffers=25
blocksindatabasebuffers=20000
database=epicor905
displayname=defaultConfiguration
internalcodepage=utf-8
locktableentries=204800
logcharacterset=utf-8
maxservers=43
maxusers=136
otherargs=
servergroups=epicor905.defaultconfiguration.odbcgroup,
epicor905.defaultconfiguration.mfgsysgroup
spinlockretries=50000
Then you can find the Pilot, test, and train ones after that one, this is
what your test one will look like.
[configuration.epicortest905.defaultconfiguration]
asynchronouspagewriters=2
blocksindatabasebuffers=20000
database=epicortest905
displayname=defaultConfiguration
internalcodepage=utf-8
locktableentries=204800
logcharacterset=utf-8
maxservers=43
maxusers=136
otherargs=
servergroups=epicortest905.defaultconfiguration.odbcgroup,
epicor905.defaultconfiguration.mfgsysgroup
spinlockretries=50000
You may already see the problem, you may not.
If you look at the servergroups line you will notice it is referencing the
mfgsysgroup from the Live/Production DB instead of for the test DB.
Manually edit that line to say:
servergroups=epicortest905.defaultconfiguration.odbcgroup,
epicortest905.defaultconfiguration.mfgsysgroup
Just type test into the line after the epicor and before the 905. Do not
type anything else anywhere else, do not adjust line spacing to make it look
better or anything else, this will most likely cause the file to become
corrupted.
Repeat as needed for the other databases.
Then save the file and start up the Admin Service again, make sure that all
DBs and appservers etc are still there when you open the OE Management
website, if not then the file was corrupted. In which case, go back and copy
the copy of the original you made and replace the one you just corrupted.
Repeat as necessary til you get it to work.
Ned
Alternative Technology Partners
-----Original Message-----
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
Doma Reddy
Sent: Wednesday, February 16, 2011 5:05 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Port Numbers Duplication in Open Edge Management
Explorer(Web Based tool to manage App Servers)
Did anybody find that in the New webbased Tool to manage App Servers "Open
Edge Management Explorer", if we change the Mfgsys pot number on one DB it
changes on all the DB's for some reason if you change the port number on
pilot, it changes to the same port number on Main DB, TestDB & Train DB.
Â
Any work around to resolve this.
Â
Thanks,
Doma.
[Non-text portions of this message have been removed]
------------------------------------
Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must have
already linked your email address to a yahoo id to enable access. )
(1) To access the Files Section of our Yahoo!Group for Report Builder and
Crystal Reports and other 'goodies', please goto:
http://groups.yahoo.com/group/vantage/files/.
(2) To search through old msg's goto:
http://groups.yahoo.com/group/vantage/messages
(3) To view links to Vendors that provide Vantage services goto:
http://groups.yahoo.com/group/vantage/linksYahoo! Groups Links