CONSOLEMAIN.EXE Buffer overrun. Another application Freezeup

[Ken_Mahren]

Having this problem whenever Conslemain tries to connect with a server that is having a issue with BESRS agent (which is not all that uncommon).

The Console on the main BESRS server FREEZES and all I can do it End Task. When trying to reopen the console, it trys to connect to the same server that is having issues.. (I cannot reboot this server till evening) so in effect I can't do anything.

It seems that when the Console cannot communicate with a protected server the Visual basic C++ goes in to a buffer overrun error and has no routines to kill the process...

Here is the event log and error message:

Microsoft cisual C++ runtaime library
BUFFER OVERRRUN DETECTED. CONSOLEMAIN.EXE


Event Type:Error
Event Source:Application Hang
Event Category:(101)
Event ID:1002
Date:3/12/2007
Time:10:00:29 AM
User:N/A
Computer:BACKUPSVR
Description:
Hanging application ConsoleMain.exe, version 6.5.0.17171, hang module hungapp, version 0.0.0.0, hang address 0x00000000.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 48 61 6e 67 ion Hang
0010: 20 20 43 6f 6e 73 6f 6c Consol
0018: 65 4d 61 69 6e 2e 65 78 eMain.ex
0020: 65 20 36 2e 35 2e 30 2e e 6.5.0.
0028: 31 37 31 37 31 20 69 6e 17171 in
0030: 20 68 75 6e 67 61 70 70 hungapp
0038: 20 30 2e 30 2e 30 2e 30 0.0.0.0
0040: 20 61 74 20 6f 66 66 73 at offs
0048: 65 74 20 30 30 30 30 30 et 00000
0050: 30 30 30 000

I cannot believe Symantec could release such a buggy product and then offer such horrendus support.

[Bill_Felt]

Hi Ken,

The issue you are describing is one that clearly needs some expert eyes at Symantec.  I was going to suggest you contact technical support, but it appears from your message you've already tried that and had a bad experience.

I know how frustrating it can be to have a bad support experience.  I'm afraid I don't have the technical knowledge to help much with your issue in this forum.

:(

[RonV]

I had this issue when I used a 6.02 version and had more than a dozen clients listed. There was an article posted which stated that you had to increase the size of the thread pool.

It says livestate 3 but I found thisworked for LS 6 as well. Don't know if helps for later versions.

Situation:
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

1. On the Windows taskbar, right-click Start, and then click Explore.
2. 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.
   
3. In the right pane, locate and right-click consolemain.exe.config.
4. Click Open With >Notepad >OK.
   The consolemain.exe.config file is a text file. Any text editor will work in this case.
5. Locate <Options /> and type the following text:
   
   <Options ThreadPoolSize="100"/>
   
   
6. On the File menu, click Save.
7. Exit Notepad or the text editor.

To modify the V2i Protector configuration file

1. Right-click Start, and then click Explore.
2. 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.
   
3. In the right pane, locate and right-click v2iconsole.exe.config.
4. Click Open With >Notepad >OK.
   The v2iconsole.exe.config file is a text file. Any text editor will work in this case.
5. Locate <Options /> and type the following text:
   
   <Options ThreadPoolSize="100"/>
   
   
6. On the File menu, click Save.
7. 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.