RMS service is disabled for publishing for this user - microsoft-information-protection

When trying to apply a label using file api Suddenly started getting this error "Something bad happened: RMS service is disabled for publishing for this user.,ServiceDisabledError.Extent=User"
Does anyone have any idea?

Related

HTTP 500 Internal Server Error - Azure Bot Serivice

I have developed a bot on node.js as a teams app using the yo teams generator. The bot is hosted and deployed on an azure app service web app. The bot was working fine all the while, but started throwing http 500 internal server errors in the past couple of weeks.
I am not sure what has changed, but I am trying to fix this issue but not finding any leads and useful information from appInsights or the trace logs. All I see is the below exception being thrown in appInsights:
"POST to the bot's endpoint failed with HTTP status 500"
The bot works perfectly fine locally, when debugging through ngrok. Please let me know how I can fix this or where I can look for useful logs to help resolve this.
I was able to resolve this with MS on a support ticket. Looks like the fix is to update the configuration setting to reflect the latest version of node from 12.13 to 16.13.0 in the app service config section.

Unable to login to UI of Ansible Tower - get error as "Failed to access user information. GET returned status: 500"

I'm receiving error:
Failed to access user information. GET returned status: 500"
while trying to access Ansible Tower.
After I dismissed the error, it keeps prompting to login again and again.
Can Anyone suggest what can be done to troubleshoot this error?
You should confirm all the services have properly started using
ansible-tower-service -status
or
ansible-tower-service -query
Can Anyone suggest what can be done to troubleshoot this error?
The error message "500 Internal Server Error" indicated in general that the service itself is running.
According Troubleshooting Tower you may review the log files
Tower server errors are logged in /var/log/tower. Supervisors logs can
be found in /var/log/supervisor/. Nginx web server errors are logged
in the httpd error log. Configure other Tower logging needs in
/etc/tower/conf.d/.
The message "Failed to access user information" indicates that the database with user information might not be available or accessible.
For further troubleshooting more information will be necessary like
Was it working before?
If so, what might have changed?
Which information does the log files provide?
Which information does the command ansible-tower-service -status give?
Based on the findings one may proceed further.

Connect PowerBI to Google Big Query through a proxy server (corporate network)

We are trying to make a connection from PowerBI Desktop, to the Google Big Query Database. Upon starting the app and immediately after trying to make the connection to the Google Data Source, we get the error below:
Unable to Connect
We encountered an error.
Details: "ODBC: ERROR [HY000] [Microsoft][DriverOAuthSupport] (8701) Error interacting with REST API: Couldn't resolve host name
ERROR [HY000] [Microsoft][DriverOAuthSupport] (8701) Error interacting with REST
API: Couldn't resolve host name"
I suppose that it has something to do with the proxy used inside our corporate environment but i haven't found anything so far on what urls/ports should be opened in order for this connection to work.
Please do keep in mind that this is a new business need and it is not something that worked and stopped working.

Trying to log in on parse server gives "internal server error"

My iOS app has suddenly started giving this error message when logging in or creating a new user in the app:
[Error]: {"code":1,"message":"Internal server error."} (Code: 1, Version: 1.15.4)
Here is the pickle. The app works fine on an earlier version (version 4.4.0) that I have on my iPad. Here I can log in and create a user, and I can add items and delete items while in sync with the server. In the new version of the app (4.4.1) nothing has changed with regards to the code on my login page. I can still fetch data from the server in the app as well, but logging in and creating a user gives the internal server error.
I got my server on Heroku and the database on MongoDB. The database is available and running. However, the server Heroku got several failed throughputs (5xx code) during a day. This says to me that something is going on with the server side of things.
Does anyone know where to turn to next? I can't seem to get my head around where the issue is rising from. I have already sent a mail to Heroku, so I'll make an update when I receive an answer.
But basically, I need help to know what would be my next step to figure out what is causing the error?

MQ Console - Queue manager unavailable, despite it being active

I am testing a deployment of MQ 9.0.1 using Docker, and trying to administer this instance using the Web console. However I am receiving a warning when attaching widgets stating the "Queue manager unavailable".
Warning messages
In the console I can see my Queues are running and have created local queues and can run commands against them.
Also if I try to modify the Queue security records I get another error:
Failed to get authority recordsWMQWB0003E: The request could not be completed due to an internal web application server error.
Any thoughts or suggestions around this issue?
There is no definitive fix for MQ9.0.1 but upgrading to use MQ9.0.2 will resolve issues with hosting MQ Console on linux.

Resources