Page 1 of 2
Alpha Installation Problem
Posted: Tue Apr 24, 2012 4:03 pm
by miplatt
We tried to install the newest Alpha today. After going through the normal install processes, the last step seemed to take a very long time (a command box appears for a while as opposed to a few seconds).
Then, the ClayCentral service did not start on its own as it usually does. When we try to start the service manually from the services menu, it attempts to start but eventually times out and says that it cannot start.
We tried this process 3 times just to make sure but we received the same results.
As a result, for now, we have reinstalled our former Clay version (9.0.0a87) and it easily installed.
Any idea what might have happened? Suggestions?
Re: Alpha Installation Problem
Posted: Tue Apr 24, 2012 5:47 pm
by ZevToledano
The latest version works on other machines we tested so I'm not sure. Perhaps there were locked files and you needed to reboot after the install. Did you try a reboot?
Also try running the new ClayCentral.exe manually (i.e. run the program once from Program Files\Digital-Clay\Central\, not by using Windows Services) and let me know if there is an error. If it loads fine this way, kill the ClayCentral.exe process and try again via Windows Services.
Finally, check the ClayCentral.log file (same location) after it fails to start and let me know if there is anything there.
Re: Alpha Installation Problem
Posted: Wed Apr 25, 2012 2:52 pm
by miplatt
Ok, thanks for the suggestions.
Some of our personnel are leaving for trips and prefer not to do any installations until they return so this may wait a few weeks.
Will plan to keep you updated.
Re: Alpha Installation Problem
Posted: Mon Jun 11, 2012 4:35 pm
by miplatt
ClayCentral has stopped a few times in the last few days and we have had to start the service manually.
Now we have tried to upgrade to 9.0 and when we try to run the claycentral service, not only does it fail, but it also causes the whole server to restart. In addition, we could not find a central.exe in C:\Program Files\Digital-Clay\Central to run manually.
We then tried to reinstall the previous version. Now central still does not start and we are not able to find a central.exe in C:\Program Files\Digital-Clay\Central to run manually.
After both processes, the central.log appears blank.
In addition, the attached virus message came up during the new version's installation.
Suggestions? Currently Central is down and our office is not able to use the system.
Re: Alpha Installation Problem
Posted: Mon Jun 11, 2012 4:51 pm
by miplatt
Reinstalled version 9.0.0a87 and it works for now
Re: Alpha Installation Problem
Posted: Mon Jun 11, 2012 5:23 pm
by ZevToledano
Avira detects Clay exes as false positives. They confirmed this months ago and promised to fix it. Perhaps try updating Avira. If that doesn't work, exclude all Clay exes in the antivirus program settings, and try again.
Re: Alpha Installation Problem
Posted: Tue Jun 12, 2012 2:58 pm
by miplatt
Disconnected the Avira Anti Virus Server and then tried installing the new clay.
At the end of installation, the net.exe box hangs for quite a while (see attached photo) and then eventually disappeared.
The Central service did not start and when we tried to start it manually, we eventually received an error message (see other attached photo).
Also, still could not find the exe files. Are they getting caught somewhere?
More Suggestions?
Re: Alpha Installation Problem
Posted: Tue Jun 12, 2012 3:11 pm
by miplatt
Stopped the Avira service and now we were able to install on the server successfully. The exe appears and the service started automatically.
This is good!
Re: Alpha Installation Problem
Posted: Tue Jun 12, 2012 3:24 pm
by ZevToledano
Yes it's good but if you restart the Avira service, it may run a scan and delete the files again. You need to add them as exceptions so that it ignores all clay exes.
Re: Alpha Installation Problem
Posted: Tue Jun 12, 2012 3:29 pm
by miplatt
Yes, it seems that you are correct. After restarting Avira and then starting ClayStation, Avira jumps on it and reports it as malware.
Ok, will work on adding these as exceptions.