|
You are not currently logged on. You must be logged on in order to post. Log on
Or Create a new account |
|
|
|
 |
AutoMate Discussion |
 |
 |  |
|
Hide | |
| BETA |
|
| · | AutoMate 10 & AutoMate BPA Server 10 - Public Beta |
| AUTOMATE |
|
| · | Automate 11 |
| · | AutoMate 10 |
| · | AutoMate 9 |
| · | AutoMate 8 |
| · | AutoMate 7 |
| · | AutoMate 6 |
| · | AutoMate 5 |
| AUTOMATE BPA SERVER & AUTOMATE ENTERPRISE |
|
| · | Automate Enterprise 11 |
| · | AutoMate BPA Server 10 |
| · | AutoMate BPA Server 9 |
| · | AutoMate BPA Server 8 |
| · | AutoMate BPA Server 7 |
| GENERAL |
|
| · | General Discussion |
| · | Sample Tasks |
| · | Suggestions |
| · | Lounge |
| KNOWLEDGE BASE |
|
| · | KB Articles |
| · | AutoMate / Automate |
| · | AutoMate BPA Server / Automate Enterprise |
| · | Triggers / Conditions |
| · | Actions / Activities |
| · | Task Builder |
| Automate | |
| AM11 | 11.0.6.11 |
| AutoMate | |
| AM10 | 10.7.0.3 |
| AM9 | 9.0.5.4 |
| AM8 | 8.0.9.0 |
| AM7 | 7.1.3.0 |
| AM6 | 6.2.8.0 |
| AM5 | 5.5.5.1 |
Automate Enterprise
AME11
11.0.6.11
AutoMate BPA Server
BPA10
10.7.0.3
BPA9
9.0.5.4
BPA8
8.0.9.0
BPA7
7.1.3.0
| Insite | |
| 2.2 |
|
Topic Title: Server migration issue.. Topic Summary: migration from server 2003 to 2008 failed Created On: 08/29/2013 11:03 AM Status: Read Only |
Linear : Threading : Single : Branch |
 Search Topic |
Topic Tools
|
 08/29/2013 11:03 AM
|
||||
|
Hi, I know this is some old software and an unmonitored forum but..
While we're using bpa8/9 we still have a few tasks running on our old BPA7 server, today we were trying to install and use the bpa7 server on an new server (windows server 2008) instead of the old windows server 2003 that has been running this software for a couple of years now. the issue that occured was the following, after installing the servercomponent on the new windows 2008 machine, connecting to the existing sql datastore, and re adding all the licensces we pointed the DNS name used by all our agents to the new server. What happened was no agent connected, some with the error "attempting reconnection to server..." but a few with this error "automate because the agent limit has been reached". Either way we had to go back to using the old Windows Server 2003 machine and pointing the DNS back to it as well, that made the agents come back online. Any ideas as to what might have gone wrong? While the agents could not connect tto the new server with the aforementioned error, I'could connect to it using the dserver management console...
------------------------- Daniel Grip |
||||
|
|
||||
|
08/29/2013 11:47 AM
|
||||
|
Daniel,
"agent limit reached" makes me think of a missing serial number in the licenses of the new installation. ?? Are the HKEY_LOCAL_MACHINE\SOFTWARE\Network Automation\AutoMate BPA Server 7\Licensing identical in both machines ?
------------------------- Jean Delfosse - Automate Beta Tester Win7 Pro 64 bits -Win XP Pro SP3 32 bits - AM8, AM7, BPA10, BPA9, BPA8, BPA7, AM6 Enterprise, AM4 
|
||||
|
|
||||
|
08/29/2013 11:19 PM
|
||||
|
Hi Jean,
I made sure to add the same licenses, I even remowed them and re-added them just in case since I had the same Idea. But now looking at the registry on both machines I can see there is one licens entry that is not included on the new server. But either way the ones that were included are more than enough for all the agents that were trying to connect. But who knows..
------------------------- Daniel Grip |
||||
|
|
||||
|
08/30/2013 03:00 AM
|
||||
|
Indeed, who knows ? Try adding the missing one.
I have no better idea.
------------------------- Jean Delfosse - Automate Beta Tester Win7 Pro 64 bits -Win XP Pro SP3 32 bits - AM8, AM7, BPA10, BPA9, BPA8, BPA7, AM6 Enterprise, AM4
|
||||
|
|
||||
FuseTalk Enterprise Edition v4.0 - © 1999-2021 FuseTalk Inc. All rights reserved.
Category Survey