|
| [WX20] HFCS MantaManager eating 30% CPU |
| Iniciado por guest, 01,sep. 2015 14:58 - 4 respuestas |
| |
| | | |
|
| |
| Publicado el 01,septiembre 2015 - 14:58 |
Hi,
I have the impression that since the upgrade to Windows 10 MantaManager is going bizerk...
It eats 30% CPU all the time heating up my ultrabook to unknown heats.
Also I can no longer connect to the server control center without getting an error that the server is not available.
Parameters:
Server name: localhost
Server Port: 4900
I already uninstalled the HyperFile Server and re-installed it completely but I have the same issues after the installation.
Anybody has already seen something similar?
TIA,
Peter H. |
| |
| |
| | | |
|
| | |
| |
| Publicado el 02,septiembre 2015 - 00:21 |
| Have HFCS 20 running under Windows 9/10. Haven't had that issue, but have had problems with CC hanging after in completes optimize indexes. |
| |
| |
| | | |
|
| | |
| |
| Publicado el 02,septiembre 2015 - 11:35 |
Hi all,
OK, managed to solve the high CPU load after a re-install under HFCSLocalHost:4900 instead of LocalHost:4900 but with an empty database folder this time.
So the existing DB's are causing some issues on mantamanager apparently explaining the high cpu load.
I see a subfolder _hyl in the DB directory with 19 part_nr.hyl files.
BUT, I still can't connect to the db-server with the HFCS CC.
I get the popup message: Unable to Access the specified Server after entering the server login data.
Even after shutting down McAffee firewall and Anti-Virus software...
Any clues out there?
Thanks!
Peter |
| |
| |
| | | |
|
| | |
| |
| Publicado el 02,septiembre 2015 - 18:53 |
Hi,
I'm getting crazy trying to get my local HFCS C/S back up an running.
I reinstalled about any version of HFCS V20 (French/English 32/64) on a number of ports and I cannot get my local HyperFileSQL server up.
Here's what I see:
- Mantamanager.exe/Mantamanager64.exe services running (Sysinternals tells me it listens on port 4999)
- HyperFile server service running (Systinternals tells me it listens on port 4900)
Next when I start the HyperFile Control Center and try to access the server I get a popup message after 30 seconds (smells like a timeout) saying:
- Unable to access the specified server
Next:
- All logging is turned on on the HyperFile server config file HFConf.ini but... No log is written whatsoever.
- Looking in the Windows Event journals there is nothing that indicates an error or warning
I am really getting out of clues here and have also raised a ticket with TS.
However, I am afraid I will get the standard 'We cannot replicate' response on this...
So to any gurus out there: any hints, any clues, any ideas???
I'll be most grateful!
Thanks in Advance,
Peter H. |
| |
| |
| | | |
|
| | |
| |
| Publicado el 02,septiembre 2015 - 20:19 |
Hi All,
Found it... But it must be due to a bug in MantaManager somehow...
If I use MachineName:4900 (Where machine name is my computer name) it works.
All settings refer to the HF server as "HFCSLocalHost" on port 4900 (HFConf.ini, service name in execution which is Hyper File Server: HFCSLocalHost etc...) but apparently this fails.
Even after logging on to the control center the HF Server is called in the treeview HFCSLocalHost...
I'll scan the registry to see if there is something sticky over there but somehow the mantamanager and hyper file server are not using the configured name to talk to each other.
Cheers,
Peter H. |
| |
| |
| | | |
|
| | | | |
| | |
|