When i try to launch the google assistant it crashes displaying the following error.
And when it reply it either say :
"There as been an error try in a few second"
"There as been a glitch"
ON_MUTED_CHANGED:
{'is_muted': False}
ON_START_FINISHED
[19218:19229:ERROR:speech_processing_task.cc(646)] Detected communication error: Downstream closed prematurely.
ON_CONVERSATION_TURN_STARTED
[19218:19229:ERROR:speech_processing_task.cc(646)] Detected communication error: Downstream closed prematurely.
[19218:19229:ERROR:assistant_output_handler.cc(589)] Failed with a general speech recognition error
ON_ASSISTANT_ERROR:
{'is_fatal': False}
ON_RESPONDING_STARTED:
{'is_error_response': True}
ON_RESPONDING_FINISHED
ON_CONVERSATION_TURN_FINISHED:
{'with_follow_on_turn': False}
[19218:19229:ERROR:speech_processing_task.cc(340)] S3 connection has timed out: No data from S3
[19218:19229:ERROR:speech_processing_task.cc(646)] Detected communication error: Downstream closed prematurely.
I am connected to the raspberry pi via ssh and can ping so i don't think it is a connection issue.
This my first post let me know if there is something i need to change or details i might have forget.
[upadate] i checked on myactivities and nothing appear in the logs but when I try with my smartphone it logs it properly
Also I updated my raspberry pi3 to the latest version and still no change in the error log
I had the same problem.
The thing was that the google assistant api wasn´t enabled.
do ctrl+c and run this command with env
python -m googlesamples.assistant.grpc.pushtotalk
When it says Press enter to send a new request, press enter and say something.
It will give you an error with a lot of command lines.
The last paragraph is important.
It´s here :-
PERMISSION_DENIED, Google Assistant API has not been used in project integrigate before or it is disabled. Enable it by visiting https://console.developers.google.com/apis/api/embeddedassistant.googleapis.com/overview?project=projectname then retry.
If you enabled this API recently, wait a few minutes for the action to propagate to our systems and retry.)>
copy and paste the link in your browser and click enable api.
once it is finished
run the command below
google-assistant-demo.
It should work now.
Yusonious
Related
We are no longer able to submit our action to the Alpha and/or Preview channels for testing.
From the Actions Console:
Clicking the Deploy tab
Start New Release
Select 'Alpha' Channel
Clicking Submit
Normally, the page would now refresh and show the draft version being deployed to Alpha.
Instead, we get this error: "Your submission of Version XX was denied"
Note: This error appears immediately, the Action did not go through review and get denied; the submission itself failed. We're not getting any more error info on why the submission failed, and also didn't get any info by email. (Normally, when the Action gets reviewed and there's a problem, we get an email explaining what we should do to fix it)
When trying to deploy the Action from the Google Actions SDK (gactions), a similar error appears:
powershell
PS C:\src\google-action\definitions> gactions push
Pushing files in the project "gluco-check-prod" to Actions Console. This may take a few minutes.
Sending configuration files...
Waiting for server to respond...
Done. Files were pushed to Actions Console, and you can now view your project with this URL:
https://console.actions.google.com/project/gluco-check-prod/overview.
If you want to test your changes, run "gactions deploy preview",
or navigate to the Test section in the Console.
PS C:\src\google-action\definitions> gactions deploy preview
Deploying files in the project "gluco-check-prod" to Actions Console for preview.
This may take a few minutes.
Sending configuration files...
Waiting for server to respond.
It could take up to 1 minute if your cloud function needs to be redeployed.
[ERROR] Server did not return HTTP 200.
{
"error": {
"code": 500,
"message": "Internal error occurred"
}
}
Again, there's no info other than this 500 Internal Server Error.
I have also tried deploying the exact same version that we have currently in Production, and the submission still fails.
Am I overlooking something, or is this an issue on Google's side?
Likewise, we've been unable to submit any releases to preview, alpha, beta or production channels for almost a week.
CLI throws 500 errors, website shows a blank page and all attempted submissions show up minutes later with "submission failed."
Emails to support under the topic Deployment Issues have gone unanswered as well, so there's no way to figure out what's going on or how to fix it.
I'm trying to deploy an application via web deploy to a windows 2012 r2 server.
First tried installing iis, web deploy using the msi. After getting an unreachable error I saw somewhere that I needed wmsvc to be installed and installed it via powershell command Install-WindowsFeature Web-Mgmt-Service.
I stopped getting the unreachable error and started getting this error ->
Error: Could not complete the request to remote agent URL 'http://xx.x.xx.xx:8172/MSDEPLOYAGENTSERVICE'.
Error: The operation has timed out
On the server's event viewer under system I get the following error ->
A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 10. The Windows SChannel error state is 1203.
Any idea of what could be going on? Did I miss something on the installation?
After this I also tried installing everything but without iis and I get the same error.
So, this is really not a PoSH issue.
Maybe you should consider movin gthis question to another forum.
Anyway, you have either real server config issues (this can sometimes mean wipe and rebuild - very ugly option - but if it's a virtual machine and you have a snapshot, just roll back), or an app causing this.
Typically for Schannel type of error, it has to do with application or service in machine not able to complete any SSL connection sort of connection.
The error state parameter of 1203 means client error connecting to server, ie invalid ClientHello from the client
See if you can collect more data by...
https://support.microsoft.com/en-us/help/260729/how-to-enable-schannel-event-logging-in-iis
I realized this is an old question, but in case somebody ran into the same issue, here are my solution.
I had to follow this guidelines : https://learn.microsoft.com/en-us/aspnet/web-forms/overview/deployment/configuring-server-environments-for-web-deployment/configuring-a-web-server-for-web-deploy-publishing-web-deploy-handler
Copy the resulting publishsetting file. In the Publish/Profile page import it.
In the Publish/Connection page, change the server to the server address with the 8172 port. Add the password. Change the Destination URL to the site to go to after the publish is completed.
Then after Validate connection was completed, go ahead and publish it!
Yesterday our extracts failed to refresh with the following message (image extract_error):
Failure: Failed 1 time. Sign in failed.
Resolution Details: Check the Data Connection page for necessary updates to an access token or embedded credentials.
I verified that all our passwords were unchanged and test connections which were successful.
The tableau dashboards now give an error message saying:
HTTP 404:
Unable to connect to the server "localhost". Check that the server is running and that you have access privileges to the requested database. (image tableau_error)
Further, when I opened the Server Status page, I saw that our one of our two Vizql, backgrounder and data servers were down. We have two of each and only one of them is active for all three of them. (image server_status)
So, I decided to remote desktop into the server and run the tabadmin status -v command and strangely it is showing that all processes are running. (image tabadmin_status)
Finally, I opened a case with Tableau Customer Portal and letting them know about this issue (they asked me send them the log.zip file) but the mean time I was trying to problem solve this issue. Any help would be really appreciated.
After trying a lot of things, one process seemed to work.
Stopped the tableau server
Configured it to run 1 Vizql server process instead of 2
Started the server again
Finally, it worked. The status page now shows all the processes are active.
Hopefully, this helps someone who is facing a similar problem.
This may be caused by a firewall issue. Since tabadmin status -v returned all as "running" the cluster is healthy and this is a false alert. The firewall rules could be allowing just the first port and not the entire range (see https://onlinehelp.tableau.com/current/server/en-us/ports.htm) to respond to requests from the application server to build that fancy table with the green and red boxes.
The firewall can be reverted/altered behind the scenes for a number of reasons, usually windows updates or regular group policy synchronization.
Try disabling the windows firewall (https://www.faqforge.com/windows-server-2016/turn-off-firewall-windows-server-2016/), or add an inbound rule allowing access to all ports if your org policy doesn't allow you to actually turn it off. (Follow the steps here, except use "All Local Ports" instead of "Specific Local Ports" https://www.parallels.com/blogs/ras/configuring-windows-server-firewall-for-parallels-ras/)
I had a similar problem and followed these similar steps that Sravee mentioned above to bring the all processes back to active.
Stopped the server
Change the configuration for VizQL server from 2 to 1
Started the server
Enter the licence key (else the server status page will show unlicensed error)
Note: This does not bring the site back but this step is for 'tricking' VizQL server
Stopped the server again
Change the VizQL configuration from 1 to 2 now.
Start the server
Enter the license key
This steps did bring back the server back to active for us. Posting to see if this helps who faces the same problem. Thank you so much.
Facing below error for quite a long time today. Is this frequent?
We are trying to run a sample app locally [connecting to bluemix blockchain]
Also tried to install/deploy directly into blockchain.
Both results in same error on login page itself. Also gets ERR 500/
Waiting on the node server to open up so we can talk to the blockchain. This app is likely still starting up. Check the server logs if this message does not go away in 1 minute.
This application cannot run without the blockchain network :(
The "starter network" blockchain has been experiencing intermittent capacity overflow issues. We currently have availability; have you tried this recently? Try again andlet us know if you get the same error. If yes, please open a support service ticket via Bluemix dashboard.
Hope this helps, and thanks for using blockchain!
I'm trying to enable MSMQ on my development computer (running Windows 7).
I go to turn windows features on or off -> Microsoft Message Queue (MSMQ) Server Core -> Check MSMQ Active Directory Domain Services Integration AND MSMQ HTTP Support.
When I click OK, I get the error "An Error has occurred. Not all of the features were successfully changed." -> Click OK -> "You must restart your computer to apply these changes".
I've clicked Restart Now and Restart later and no matter what, same issue every time.
If I selected Restart later and go into Services...I see Message Queuing (stopped), and if I try to start the service, I get the error "Windows could not start the Message Queuing service on Local Computer. Error 0x80070005: Access denied."
I checked my privileges and I am an Admin on the machine. Just to be safe, I even logged into the machine as the actual Administrator. Same scenario.
Furthermore, when I go into the Event Viewer, I check the Application logs. I have an error with MSMQ as the Source. EventID: 2076, Error: The logger files cannot be initialized. The file QMLog in the Msmq\Storage folder is corrupted or absent. Error 0x80070005: Access denied.
If I check the System Logs, I see another error with the source being Service Control manager. Error eventId: 7023, Error: The Message Queuing service terminated with the following error: %%-2147024891
When I look up the error codes on Microsoft, there is NOTHING.
I had something like this - not sure how it came about as I always had AD integration turned ON for my MSMQ (as I needed it) but somewhere along the line, it got turned off and I couldn't turn it back on again via Control Panel - I would get the error behaviour (and restart!) that the OP describes. To fix it, I accessed my machine via the AD services manager app on one of our domain servers and deleted the "msmq" object that was under it.
I restarted my local MSMQ service on my machine AND rebooted (not sure which or both was required) and then when I checked my local registry entries, it indicated I was correctly running in AD mode once again. Everything started to work again after that.
This link was helpful in giving me the right direction to go in: Technet MSMQ delete stale objects article