Symantec LiveState Recovery Advanced Server console shows "connecting" but never connects
| Article:TECH109043 | | | Created: 2005-01-16 | | | Updated: 2006-01-28 | | | Article URL http://www.symantec.com/docs/TECH109043 |
Problem
After LiveState Recovery Advanced Server 3.0 is installed, you connect to six computers being managed by the console without any problems. When you attempt to connect to more than six computers, the message "connecting" appears; however, you cannot connect to any of the computers. You want to know how to fix this problem.
Solution
There is a limitation on the number of connections, computers in the console, LiveState Recover, or V2i Protector allows. To fix this problem, modify the following thread pool configuration file:
- LiveState Recovery Advanced Server: ConsoleMain.exe.config
- V2i Protector: V2iConsole.exe.config
To modify the LiveState Recovery configuration file
- On the Windows taskbar, right-click Start, and then click Explore.
- Navigate to the Console folder.
The default path is as follows:
\Program Files\Symantec\LiveState Recovery\Standard Server 3.0\Console
If the default path was not selected when LiveState Recovery was installed, navigate to the appropriate location.
- In the right pane, locate and right-click consolemain.exe.config.
- Click Open With > Notepad > OK.
The consolemain.exe.config file is a text file. Any text editor will work in this case. - Locate
and type the following text:
<Options ThreadPoolSize="100"/>
- On the File menu, click Save.
- Exit Notepad or the text editor.
To modify the V2i Protector configuration file
- Right-click Start, and then click Explore.
- Navigate to the Console folder. The default path is:
\Program Files\PowerQuest\V2i Protector 2.0\Console
If the default path was not selected when LiveState Recovery was installed, navigate to the appropriate location.
- In the right pane, locate and right-click v2iconsole.exe.config.
- Click Open With > Notepad > OK.
The v2iconsole.exe.config file is a text file. Any text editor will work in this case. - Locate
and type the following text:
- On the File menu, click Save.
- Exit Notepad or the text editor you are using.
Check agent server log file
This error can also occur if the server log/application log on the agent server is full. To resolve this problem, clear the server log/application log and attempt the connection again.
|
|
Legacy ID
2005021607291860
Article URL http://www.symantec.com/docs/TECH109043
Terms of use for this information are found in Legal Notices
Thank you.