Open dmantz7 opened 6 years ago
When running the connector outside the service, please make sure you are running the exact command that the service is running. It will be the executable but also a --config-filename with the path of your config file (probably something like c:\ProgramData/Google/...).
You can also try pulling the event logs, see:
https://github.com/google/cloud-print-connector/wiki/Windows-Event-Log-and-Troubleshooting
I got the same error when I tried to install version 1.16 on Windows 7 Ultimate with latest patches.
The MSI installer tried to start the service, and failed and said I do not have privilege, but I was administrator and gave all privileges it asked for.
I copied the exact command line from the service and ran it in command prompt, both with and without administrator. Here's console output:
C:\Windows\system32>"C:\Program Files\Google\Cloud Print Connector\gcp-windows-c
onnector.exe" --config-filename="C:\ProgramData\Google\Cloud Print Connector\gcp
-windows-connector.config.json"
Google Cloud Print Connector.info(3): No config file was found, so using default
s
Google Cloud Print Connector.info(3): Google Cloud Print Connector for Windows v
ersion 1.16-windows
Google Cloud Print Connector.error(1): FATAL Local printing has not been impleme
nted in this version of the Windows connector.
Incorrect function.
I reviewed Windows Event Log and here's error message:
The description for Event ID 1 from source Google Cloud Print Connector cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
FATAL Local printing has not been implemented in this version of the Windows connector.
Because this is a new install I do not know what to do with the json file. I don't have it anyway.
I ran gcp-connector-util.exe init
, entered the code, waited it to finish, and nothing happened.
In the last couple weeks, we have started to see printers failing to print jobs submitted to our Windows 10 device running Cloud Print Connector with the most recent version. The W10 device is fully patched. In troubleshooting, I opened up CMD and started the service using command line string. Upon the service starting via CMD, a test print job was sent. The following error message appeared within the CMD window upon receiving the submitted print job.
FATAL Local printing has not been implemented in this version of the Windows connector.
What do I need to adjust so we can resume printing via Cloud Print Connector?