The OpenVpn application needs an additional adapter to can work well. The Tap-Win32 virtual ethernet adapter will be installed during the application installation or can be added later.
Something went wrong, because I have tried everything, also running as administrator, troubleshooting, enable/disable, reinstall, but always will be going this to a failed status.
But without this adapter the connection will be failed too.
What can to do then?
It seems that the problem is solved by downloading the newest standalone Tap driver from OpenVpn repository.
UPDATE: I STILL CANNOT FIND THE STARTUP LOGS FOR KIBANA ANYWHERE.
I just installed Kibana after installing log stash on my Mac. I used brew install kabana. Then I used brew install start service cabana. Then I see the error message Kibana not ready when I access on localhost:5601. Ok, so where do I go and find why Kibana is not ready yet? I dont see any logs for it under /var/logs.
So what I need is to know where to check the logs to see what is wrong. I have already checked that log stash is running on expected port. I have seen one other response and it was some cryptic reply that it could not find it under the service name logstash. Yet no mention anywhere of service names for install. Also can we have more useful information then Kibana not ready yet like Kibana not ready yet because it could not find X or Y. Something that at least looks like its trying to help us during install. Who decides this kind of thing. Like we just see not ready yet with no mention of logs files or where they are located. Why not just startup and provide the start logs of Kabana? Would this not make more sense then just a meaningless message?
Steven$ brew services stop kibana
Stopping `kibana`... (might take a while)
==> Successfully stopped `kibana` (label: homebrew.mxcl.kibana)
coffee:log Steven$ brew services start kibana
==> Successfully started `kibana` (label: homebrew.mxcl.kibana)
I mean what a worthless error message. In fact its ambiguous as to whether there is an error at all. The absurdity is that a logging app and we are trying to hunt down the logs for this. Madness.
Found the solution reading this article:
https://logz.io/blog/elk-mac/
Looks like kibana file needs some updates before its ready. Not sure why that is not the message with a reference to the config file. Anyway still looking for kibana startup logs. I dont see them anywhere.
I have a problem when I install rabbitMQ Silently (not normal), It is installed successfully and I see the rabbitmq in services and started but when I try to run rabbitmqctl or rabbitmq-plugins I face the following error:
* Connection attempt from disallowed node 'rabbitmq-plugins1208079#WIN-IOBM5KICB89' **
I found a work around for this when I copy the .erlang.cookie from C:/{User} to C:/Windows, the problem is solved, any I dea why is this happening and if there is any other solutions for this?
The cookie is used by the underlying erlang environment to decide to allow/block the connections. More information is here
My setup:
Opertaing System: Windows 8.1
Memory: 16GB
HD: 500GB
etc. non relevant.
Issue:
I noticed the issue when my printer stopped working after a normal restart. At that point I tried to uninstall and reinstall the printer driver. The install failed.
At that point I also realized all my remote desktop connections were also failing, with not being able to find the remote host.
Here is the error I was seeing when install for the printer was failing:
can't start printer spooler service not enough resources are available to start the service
Manually trying to start the spooler service and checking in the event Viewer of windows showed that it was failing on:
Failed to schedule Software Protection service for re-start at 2014-09-13T08:09:30Z. Error Code: 0x80040154.
Further trying to restart the protection service revealed that it was failing on:
Task Scheduler service has encountered RPC initialization error in "RpcServerUseProtseq:ncacn_ip_tcp". Additional Data: Error Value: 1721.
In either case my computer had become somewhat useless as I couldn't install anything and my printer and remote desktop was broken too.
Reporting the problem just in case if someone has a similar issues.
The resolution for my problem is actually posted here, but way back so bringing it to more light:
http://social.technet.microsoft.com/Forums/windows/en-US/0c438376-1486-4ae4-9847-2de7a8767f27/task-scheduler-service-has-encountered-rpc-initialization-error-in?forum=itprovistasp
For me what worked was just to starting the prompt in adminstrator mode, running:
netsh winsock reset
and restarting my machine.
Not exactly certain of what actually fixed the issue.
When I try to install a Windows service:
c:\Windows\Microsoft.NET\Framework64\v4.0.30319\installutil
I get, what looks to be, some success messages and some failure messages. Part way down:
An exception occurred during the Install phase.
System.ComponentModel.Win32Exception: The specified service has been marked for deletion
At the end:
The Rollback phase completed successfully.
The transacted install has completed.
The installation failed, and the rollback has been performed.
The service is given an entry in the Services applet, but it is marked as "Disabled". When I attempt to change it to another state, I get a "marked for deletion" error message.
There are no messages in the Event Log. There is nothing useful in the log file created by installutil.exe (I believe it's written to the current working directory).
I have no direction to go with this. What do I do?
It turns out that the install might, or probably will, fail if that service is highlighted in the Services applet. It's safest to just close the Services applet, install the service, and then re-open the Services applet. It's really stupid.
Also, make sure to run the console as admin.
I experienced the same and the issue for me was that a service with the same name was already installed. So in order to install the new service I had to uninstall the older services. I am learning how to create and setup windows services and thus the naming conflicting. Tried uninstalling the service first through:
c:\Windows\Microsoft.NET\Framework64\v4.0.30319\installutil -u servicename.exe
Once this statement executes successfully, install your service and it should succeed without any rollbacks.
Right Click on Command Prompt and choose RUN AS ADMINISTRATOR
Then copy and paste in: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\InstallUtil.exe C:\TestService\bin\Debug\TestService.exe
Result in TestService.InstallLog is:
Installing service TestService...
Service TestService has been successfully installed.
Some times this happens due to permission issues.
Run the "Developer Command Prompt for VS 2012" as Administrator.
Then it will work.
Adding few more check's and points to solve this above issue.
Build service in release mode and take release folder files and kept in different path
Copy that path and go to visual studio command prompt window and run this bellow sample command to install the service.
Please close services.msc window if its opened , then run C:Program Files (x86)\Microsoft Visual Studio 11.0>InstallUtil.exe C:\RunLocationServices\TestService.exe
Go services.msc and select that service and click on start ,if it changed to "started" then your service running fine.
Still if issue exists then
Another Checkpoint & SOLUTION
When a service starts, the service communicates to the Service Control Manager how long the service must have to start (the time-out period for the service).
If the Service Control Manager does not receive a "service started" notice from the service within this time-out period,
the Service Control Manager terminates the process that hosts the service.
This time-out period is typically less than 30 seconds.
If you do not adjust this time-out period, the Service Control Manager ends the process.
To adjust this time-out period, follow these steps:
1.Go to Start > Run > and type regedit
2.Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
With the control folder selected, right click in the pane on the right and select new DWORD Value
3.Name the new DWORD: ServicesPipeTimeout
4.Right-click ServicesPipeTimeout, and then click Modify
Click Decimal, type '180000', and then click OK
5.Restart the computer
Still if issue exists then problem in your service code ,infinate loop may occur due to your methods/classes of service calling. Do code review of each line.
This problem is due to security, you'd better open developer command prompt for VS 2012:
RUN AS ADMINISTRATOR
and install your service. It will surely fix your problem.
I tried and the issue was resolved.