Hi,
we had Zoo running on Windows7, everything was working great.
We updated to Windows10 and now have the following problem after coldstart / rebooting the machine:
The Zoo service from the OS´ point of view is started automatically, all good.
But the license activation / usage is not done automatically.
In the Zoo admin tool we have to start it manually, which then works fine. This license activation was also done automatically on Windows7.
Anyone an idea ?
Cheers,
Lothar.
Hi Lothar,
I am not sure what this means. Are you saying that the Zoo service is not starting automatically?
– Dale
hi,
yes. windows10 starts the zoo server after reboot. but the license is not active somehow. i have to start zoo admin manually and start the service with my license there. on win7 that was also made automatically. i had not to run the zoo admin after reboot…
hope that clarifies a bit ?
cheers,
lothar.
Click Start -> Control Panel -> Adminstrative Tools -> Services. Then find the “Zoo 6” service and double-click on it. Make sure it is set to start automatically.
hi,
this configuration is properly set !
this starts automatically bit the license is not used.
it is only used / working when i start via zoo admin.
cheers, lothar.
Let me see if I understand this correctly:
1.) You restart your Windows 10 system.
2.) When you run Rhino, it cannot obtain a license from the Zoo.
3.) You check the Services applet in Control Panel and is indicates that the Zoo service should start automatically.
Question: when you check the Services applet in Control Panel, is the service started?
4.) You run ZooAdmin and now Rhino can obtain a license from the Zoo.
Question: when you run ZooAdmin, is everything grayed out? Do you have to start the service?
I’m really struggling trying to understand what you are experiencing. Any additional clarification you can provide would really be helpful - thanks.
Hi Dale,
I checked it once again, maybe I made a mistake while explaning. So step
by step:
- Reboot Win10
- Yepp, Rhino does not get a license
- In the Control Panel it´s marked as "Start Type: Automatically"
BUT: It has not started. “End” is greyed out; When I press “Start” zoo
starts running and offers the license.
Zoo Admin says then - certainly - that the license is available or in
use - depends on taken or not - so working fine.
So in general: It does not start automatically though configured to do so…
Cheers,
Lothar.
Hi Lothar,
I believe I understand. You’ve upgraded the system, that runs the Zoo software from Windows 7 to Windows 10. After the upgraded, the Zoo service no longer starts automatically even though the Services applet in Control Panel indicates that the service should start automatically. Is this correct?
If so, then this is the first we have heard of this issue.
Is there any information in the Windows Event Log that indicates why the Zoo service was not loaded automatically?
– Dale
Hi Dale,
thanks for following up so quick 
Here is what the Event Log says (XML)…
Cheers,
Lothar.
- <#> <Eventxmlns=“http://schemas.microsoft.com/win/2004/08/events/event”>
- <#>
<EventIDQualifiers=“0”>0
2
0
0x80000000000000
398
McNeel
lothar-PC2
- <#>
McNeelUpdate.RegisterProduct failed Inner Exception:
McNeelUpdateClient.ClientChannelException: There was a problem
communicating with “localhost”. Please contact your system administrator
for assistance. bei
McNeelUpdateClient.ClientChannel.HandleException(Exception ex) bei
McNeelUpdateClient.ClientChannel.RegisterProduct(CallerId userId, Guid
productID, Version installedVersion, Platform platform, Edition edition,
CultureInfo LocaleID, StabilityLevel stabilityLevel) bei
ZooService.ZooService.m_check_for_update_timer_Elapsed(Object sender,
ElapsedEventArgs e) Inner Exception:
System.ServiceModel.EndpointNotFoundException: Es war kein an
net.pipe://localhost/mcneel/mcneelupdate/5/pipe lauschender Endpunkt
vorhanden, der die Nachricht annehmen konnte. Dies wird häufig durch
eine fehlerhafte Adresse oder SOAP-Aktion verursacht. Weitere Details
finden Sie unter “InnerException”, sofern vorhanden. Server stack trace:
bei System.ServiceModel.Channels.PipeConnectionInitiator.GetPipeName(Uri
uri, IPipeTransportFactorySettings transportFactorySettings) bei
System.ServiceModel.Channels.NamedPipeConnectionPoolRegistry.NamedPipeConnectionPool.GetPoolKey(EndpointAddress
address, Uri via) bei
System.ServiceModel.Channels.CommunicationPool`2.TakeConnection(EndpointAddress
address, Uri via, TimeSpan timeout, TKey& key) bei
System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan
timeout) bei
System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.OnOpen(TimeSpan
timeout) bei
System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
bei System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout)
bei System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan
timeout) bei
System.ServiceModel.Channels.ServiceChannel.CallOpenOnce.System.ServiceModel.Channels.ServiceChannel.ICallOnce.Call(ServiceChannel
channel, TimeSpan timeout) bei
System.ServiceModel.Channels.ServiceChannel.CallOnceManager.CallOnce(TimeSpan
timeout, CallOnceManager cascade) bei
System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean
oneway, ProxyOperationRuntime operation, Object ins, Object outs,
TimeSpan timeout) bei
System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage
methodCall, ProxyOperationRuntime operation) bei
System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage
message) Exception rethrown at [0]: bei
System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage
reqMsg, IMessage retMsg) bei
System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData&
msgData, Int32 type) bei
McNeelUpdateClient.IClientService.RegisterProduct(CallerId userId, Guid
productID, Version installedVersion, Platform platform, Edition edition,
CultureInfo LocaleID, StabilityLevel stabilityLevel) bei
McNeelUpdateClient.ClientChannel.RegisterProduct(CallerId userId, Guid
productID, Version installedVersion, Platform platform, Edition edition,
CultureInfo LocaleID, StabilityLevel stabilityLevel) Inner Exception:
System.IO.PipeException: Der Pipeendpunkt
“net.pipe://localhost/mcneel/mcneelupdate/5/pipe” wurde nicht auf dem
lokalen Computer gefunden.
Hi,
the description from Windows is:
“Der Dienst “Zoo 6” wurde aufgrund folgenden Fehlers nicht gestartet:
Der Dienst antwortete nicht rechtzeitig auf die Start- oder
Steuerungsanforderung.”
This means
“Service Zoo was not started due to following error:
The service did not answer in time on the start or control command”
In the next message it complains about a timeout of 30.000ms…
Cheers,
Lothar.
hi, I’m experiencing the exact sample problem as louder. Recently upgraded from Windows 7 to Windows 10. Zoo 5.0 was working perfectly before. Now, when our license server computer restarts, zoo is not automatically starting up. As a result, I need to open zoo and hit the start button for licenses to become available every time the computer restarts. I would appreciate if you have a solution. thanks, Adam
Hi I am having this issue on Windows Server 2016, was there a resolution to this issue?
Are you using Zoo 6 SR10?
In Windows’ Services, is the Zoo 6 Service set for Automatic startup?
Yes we changed to to Delayed Automatic startup not sure if this will help?
1 Like
That’s probably worth a try.
The Zoo uses .NET. I have no idea how Windows decides when to load a specific service. If .NET was being loaded itself and not fully up and running then any tool that needs it would fail. I suppose this delayed automatic setting is a tool to address just that.
Hopefully that will work for your situation.
1 Like