I am trying to add my IP address to "Networking" in Azure Portal, so I can access my database and I get this error:
I have looked at the Activity Log but I do not see any usable information. Does anybody have an idea of why I can not update?
I can also note that my internet connection is good.
We have reproduced in our environment and got the same error. It may be because of the Invalid IP Address Format
Added the Invalid IP, got the below error
Please check your valid IP Address range and add accordingly.
As mentioned by #[Gandhi], yes it takes some time to get the refreshed Activity Log.
We got the failed Activity log after some time
Related
we've recently set up alerts for failed connections to database using Azure Monitor. We started getting a bunch of failed connection alerts from all of our databases.
After some investigation in system log using etc query
SELECT *
FROM sys.event_log
WHERE event_type = 'connection_failed'
ORDER BY start_time DESC
I can see that there are lost of 'Login failed for user.' and 'Login failed for user '%.*ls'.%.*ls%.*ls' messages.
Now I was able to find that this seems to be specifically Error 18456 with State 122 https://learn.microsoft.com/en-us/sql/relational-databases/errors-events/mssqlserver-18456-database-engine-error?view=sql-server-ver15 which according to documentation is 'Failure due to empty user name or password.'
All of our applications seem to work in a correct way but the error occurs on all 4 databases including 'master' almost all the time. I'm not sure how to debug exactly what's causing this. I've looked at some potential reasons but nothing seems to be the case.
Edit:
I just talked with some developers. They mentioned that sometimes when they login to SQL Azure Db from their local PC's using SQl management studio they have network issues after some time and they are logged out. I'm just not sure whether this is the real reason for these since logs don't tell that much.
Regards.
Please enable Auditing on your Azure SQL Database to further investigate. After that you can click "View Audit logs" and search for Event type "Login" and action not successful.
Once you filter login events, make a click on any event, scroll the window that shows the detail of the event you just clicked on, and you will see important information like IP address of the host.
If you use the dashboard available on the "View Audit Logs" you can have details by type, by IP address and by principal. Just click on the type you would like to see details, and you will get all related events, each one will all details.
Make a click on the IP addresses that you don't recognize (left side on below image), make a click on the failed login attempts for each principal (right side on below image, where you see the Pie chart).
I have an on-premise CRM 2016 instance and I can't receive any incoming emails inside of it even though when I run the test access says everything is good.
First, I'm unable to change a queue record email address, because I keep getting a SQL timeout error (doesn't matter how much time you increase the timeout it will never change) but if I try to change any other field it works and saves (but not the email field of course).
The same with the Mailbox's records, when I try to change the email it returns a SQL timeout error.
So what I did was change these emails by SQL queries, but after that the emails still won't create inside CRM.
It shows the next warning log in the event viewer:
35241 - The recipients for the email message with subject "[x]" in mailbox [email address] did not match any known records.
I'm running out of choices here, when I run the diagnosis tool on my organization it's performance is good but there must be something obstructing the communication with the SQL? Any clues?
SQL timeout error:
Unhandled Exception: System.ServiceModel.FaultException`1[[Microsoft.Xrm.Sdk.OrganizationServiceFault, Microsoft.Xrm.Sdk, Version=8.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]]: SQL timeout expired.Detail:
-2147204783
SQL timeout expired.
2018-10-10T14:14:15.5749939Z
I got the answer from Microsoft Community Forumns, thanks to Radu Chiribelea:
It's not enough to change the email address in SQL in it's base table for a record, so that this can be used for email tracking. There are other references as well - for example the EmailSearchBase. This is why you need to let the platform handle your changes.
You biggest issue here is the SQL Timeout and that is what you need to address. Since this occurs at a Create / Update I suspect there might be a deadlock somewhere. Do you have any plug-ins or workflows triggered at the time you create / update? If you disable those, do you still see the issue?
Can you enable a CRM Platform trace at a Verbose Level while reproducing the issue? This would give you a better overview of the actual timeout and you can then start from there to tackle it.
I want to ask if I am able to extract from logon EVENTDATA xml successful login events?
Why? Because somebody is trying to compromise our SQL Server and we are trying to extract IP addresses to be blocked.
I managed to help myself. I created the extended events session for the login event and started collecting data. Next I looked for the attribute of a record which stores error number when logon fails - err num 18456 - I can't remind the name of the attribute. Thanks to that I was able to find the IP addresses that where used to compromise my server. Finally I created a rule on the firewall where I blocked founded IP addresses. Attacks have stopped.
I am having a strange problem that happens randomly on a server. Some mornings, our client will call in and say their website is not working with the following error message:
The underlying provider failed on Open.
The temporary fix I found for this was to manually go in and restart the SQL Server service. Once this is done it works just fine until the next random time it happens. So my question is, does anyone know what exactly is happening? If so, how can I prevent this in the future?
I have tried searching everywhere for this with the only explanation saying that updates were being applied to the service and it wasn't restarted properly. But I couldn't find any fixes. Thanks in advance
This error:
'FCB::Open failed: could not open file (LDF file) for the file number 2. OS error: 32( The process cannot access the file because it's being used by another process)
is quite troubling and should not be occurring, unless you just restarted your SQL Service. It would easily cause the problems that you are seeing. I would take this to GoDaddy.
If you are getting this error through your Nagios check.
Make sure you deselect "autoclose" as an option on the database.
You can select the option in: Database properties -> Options
Here select at Auto Close: false
How would you troubleshoot the multisite error message:
---- NOTE: consult log file (/var/adm/rational/clearcase/log/shipping_server_log) for errors.
mkorder(2232326): Error: Store-and-forward server "/opt/rational/clearcase/etc/shipping_server" failed with status 1
We are not able tsync the vob as a result.
Make sure you check the log and the following error message after this one.
As seen in "Removing the default Storage Class", that error message can be followed by the actual cause.
One possible cause in described in "shipping_server RPC fails sending packets to a store and forward host":
There is a defect in the DNS algorithms used.
When the VOB server initiates an export, there is a request sent to the local DNS server for information on the reachability of the destination.
If the DNS server is busy or takes too long to reply, then the packet(s) get stalled in the outgoing bay even though the shipping server would have been able to forward them along.