google / cloud-print-connector

Google Cloud Print Connector
BSD 3-Clause "New" or "Revised" License
764 stars 184 forks source link

Cloud Print Connector Service could not start Error 1067 #432

Open astrugatch opened 5 years ago

astrugatch commented 5 years ago

We've had Cloud Print Connector 1.16 running in Server 2016 pretty much since it's release, today the service won't start. Just trying to see if there is a known fix without a clean reinstall or if I need to scrap the app data and start over.

astrugatch commented 5 years ago

I've uninstalled the connector and attempted to reinstall it and it gets stuck at starting service.

The ProgramData/Google folder no longer exists so I cannot run the manual service command

sicklittlemonkey commented 5 years ago

Did you resolve this? I had a similar (same?) problem installing 1.16, but installing 1.13 and upgrading seems to work OK. Hopefully I'll have time to look into it further.

ghost commented 5 years ago

I ran into the same problem when trying to install 1.16 directly. The issue seems to still persist as of 12/28/2018. I did not try installing 1.13 and upgrading to 1.16 however.

maximumdoog commented 5 years ago

I am currently experiencing the same issue on Server 2012 and I also tried uninstalling 1.16 and installing 1.13 but I receive the same error.

kirleylp commented 5 years ago

Having this issue in 13, 15 and 16. Installation stalls at Status: Starting Services. Windows is up to date. Someone help please!

Windows Server 2012 R2, version 6.3 Build 9600 Latest update: 2019-03 Update for Windows Server 2012 R2 for x64-based Systems (KB4490128)

sicklittlemonkey commented 5 years ago

@kirleylp What's in your config file? C:\ProgramData\Google\Cloud Print Connector\gcp-windows-connector.config.json

kirleylp commented 5 years ago

Just the default , I haven't modified it yet. Also left the share option blank.

sicklittlemonkey commented 5 years ago

Were the important field populated? E.g. (Of course, I have changed a few characters. ; - )

  "xmpp_jid": "1883c00e7eb9a5214044783b8b6517d4@cloudprint.googleusercontent.com",
  "robot_refresh_token": "1/HUABqV6k3AjPab1d83WONlRgL2i2HVca0kx_3FGbMza",
  "proxy_name": "7b35337e-7bc6-4f47-b74e-c5324aa5b6f5",
cujo-github commented 4 years ago

It doesn't look like this issue has been updated recently, but I've also encountered this issue, and while I don't have anything to contribute as far as the "Error 1067: The process terminated unexpectedly", I was able to get the Google Cloud Print Connector re-installed by using the following command:

"msiexec /i windows-connector-1.16-x86_64.msi startservice=no"

I had a similar issue with the service just not working so I decided to uninstall and reinstall the program, but something has made it so that the service will not start. Apparently, this version attempts to start the service as part of the installation process. I am able to start the service manually by simply copying the path to executable:

"C:\Program Files\Google\Cloud Print Connector\gcp-windows-connector.exe" --config-filename="C:\ProgramData\Google\Cloud Print Connector\gcp-windows-connector.config.json"

And it seems to work; granted it also seems to duplicate all of my printers, but when I log into a Chrome device, it has all of my printers that I have assigned to that OU, but they also appear to be offline. I'm not sure if this has to do with the program not being run as a service or not.

kenjancef commented 4 years ago

I am having the same issue on one of my School District servers. I believe it started on Wednesday (10/9/19). The Cloud Print Service just won't start. I have been troubleshooting for about 4 hours today and can't seem to find an answer. I didn't try uninstalling/reinstalling yet, but not sure if that would actually help, from what I've read. We have the EXACT same setup on 5 servers, and just one of them have issues. And we are running 1.16 at this point. Any help would be GREATLY appreciated...