Problem: I created 10 AlwaysOn Availability Groups with SQL Server without a problem. Suddenly, it stopped worked and I kept getting this ONLY on the "create the listener" part:
Msg 19471, Level 16, State 0, Line 9
The WSFC cluster could not bring the Network Name resource with DNS name 'L_MyListener' online. The DNS name may have been taken or have a conflict with existing name services, or the WSFC cluster service may not be running or may be inaccessible. Use a different DNS name to resolve name conflicts, or check the WSFC cluster log for more information.
Sometimes I also got Msg 19476. This was all maddening because one moment I was creating listeners and availability groups, feeling like a guru, and then everything stopped and I lost hours of time.
So how do you solve this? Of course, Microsoft's own suggested text in the above error description was NOT helpful.
Apparently, each listener is really creating a mini "computer" in Active Directory if you look. And... here's the kicker, a domain user can only join a computer to a domain a limited number of times and that default is 10. Who would have thought that adding listeners equates with joining users to a domain!???! Microsoft really should have made this listener thing more intuitive, at least in their description text of possible problems.
Well, on your Domain Controller, open ADSI Edit, configure it the first time to look at your default naming context of your domain, like "DC=yourname..." with the CN= rows below that. Now, right click on the "DC=" line, choose Properties and navigate down to ms-DS-MachineAccountQuota and increase the limit from 10 to something else like 100.
You may need to run "GPUPDATE /FORCE" on the SQL Servers where you want to try again to add the listener. You may also have to clean up the mess it left (i.e. delete and restore the bad attempt at setting up your group and listener) before you try again.
With SQL Server 2016 supposedly going to require each database be in its own group, with its own listener, people will hit this limit of 10 quite easily!
I hope this helps you. If so, please mark this as the answer on the left. Of course, there are other reasons why people may get this error, as in the Microsoft error now but this whole post is for people who had it working just fine and then suddenly it stopped.
Related
I am completely new to Windows Azure and we don't have many people around the office that knows the technology, and those that do are out of the office and unreachable. so I turn to the community.
I have managed to:
Export my SQL Database to Azure standards and import it in for both sites currently using it.
Publish my sites to azure.
The issue is when I try and view any of the pages that require database information. That is, lets assume I try and view the locations page of my app at somesite.azure.com/locations this is suppose to pull in all my locatons instead I get: sorry error occurred while processing your request So I thought, this is a common database issue.
I was wrong - I think (you be the judge of that).
I made a second site that shares the database of the first site, this second site has a login, which goes to the database and checks your user name and password, well upon loggin in I get the same error, but it logs me in cause I redirect, but no data is displayed due to the error.
Is there a way to log the error? because the logging I have used only saved the error pages, like 500, 404, 503 and so on. but these error pages don't tell me much of any thing.
If it is a database issue, how can I get the specific error? When working in ASP and you throw and error the screen explodes into yellow anger. now I don't exactly want that, but I do want a stack trace.
This sounds like a database issue, but it might not be. Any ideas on how to trouble shoot. I don't find azures UI to be very friendly and the docs for this kind of thing are confusing.
The reason I don't think it is a database issue is because I let the publishing from VS 2010 to Azure create its own connection stirngs in the web.config file. but the fact that I cant display any data from the database points to that being the issue.
So, we have this one project which uses Cloud Storage and BigQuery as services. All has been well.
Then, I wanted to add Cloud SQL to this project to try it out. It asked for a unique Project ID so I gave it one. (The Project ID is different than the Project Number.)
Ever since then, I've been having a difficult time accessing my BigQuery tables. When I go to the BigQuery web interface, the URL contains the Project ID instead of the original Project Number. It shows the list of datasets, but now shows the Project Number before each dataset name and the datasets are greyed out and inaccessible. If I manually change the URL to contain the Project Number instead of the Project ID, it appears to work although it shows the list of datasets in the left nav twice, one set greyed out and inaccessible and the other set seemingly accessible.
At the same time, some code that I've been successfully using in Apps Script that accesses BigQuery is now regularly failing with a generic "We're sorry, a server error occurred. Please wait a bit and try again." I'm not sure if this is related to the Project ID/Project Number confusion, or if it's just a Red Herring.
Since we actively use the Cloud Storage service of this project, I am trying to be cautious with further experimentation with this project. I'm not sure if I should delete the Cloud SQL service in this project to get it back to the way it was, or if this is a known issue with some back-end solution. Please advise.
After setting the project id, there can be a delay where BigQuery picks up the change. It should happen within 15 minutes or so, but sometimes it takes longer.
If you send the project ID I can make sure it has been updated.
I'm somewhat stuck. We have a database server which was set up and configured by a third party. It's for a third party product so unfortunately we're stuck with the way they've configured it.
Their brilliant configuration includes using the sa account to make a number of connections. For about a week now we've had connection failures filling up all our event logs, two every ten seconds. I have managed to identify that it is the master database this login failure is for.
It's definitely the sa account accessing the master database. It is not an incorrect password (which is good, because we don't know the sa password - and neither does the vendor, it seems. Yay...) because we're getting error state 16 so I believe the sa account has some problems with the master DB.
It's connecting to everything else without problem - I can see the connections made to all other databases successfully. I have checked the sa account permissions and I really can't see anything wrong. I'm at the point of restoring the master database from a backup two weeks old and wanted to open this up to you awesome people out there in case any of you have come across this before and have any alternative suggestions...
Yours hopefully...
Summer
Edit: added a screen shot of my error below:
Well my first suggestion would be get the third party vendor in there to reconfigure and fix. They made the mess, let them clean it up.
Restoring the backup might work but it is critcally important that you 1. change the sa password and 2. do not allow the software to connect using sa. I would make this a deal-no deal item with the vendor. The vendor though is terminally incompetent if they did this and I would seriously be looking at their competition to replace this badly designed system.
SQL Server 2005 DBMail.
I had all of this working, but then it just stopped. I tried starting over from scratch to no avail
The surface area configuration tool has been used to make sure the procs in msdb are active.
I've tried stopping and starting the mail service with sysmail_stop_sp and sysmail_start_sp.
I made sure that the Mail Profile is enabled in the ALert System section of SQL Server Agent. I did change the profile being used some time ago and have NOT cycled the server up and down - it would be a big deal to do this.
I've tried stopping and starting SQL Server agent.
I've confirmed that the user belongs to the msdb database and has the role DatabaseMailUserRole.
SELECT is_broker_enabled FROM sys.databases WHERE name = 'msdb'
1
dbo.sysmail_help_status_sp;
STARTED
sysmail_help_queue_sp #queue_type = 'Mail'
mail 258 NOTIFIED 2011-08-19 16:51:34.500 2011-08-19 16:51:34.500
The state used to be RECEIVES_OCCURRING when it was working.
All email queues up with a sent_status of Unsent.
I've triple checked my email credentials and they're all good. I've tried ports 25 and 2525, both of which are accepted by my provider.
I've verified that the credentials are good by setting them up in another mail client ans successfully using them to send mail.
Am at wit's end. Anyone know what could be going on?
i had this problem before, it’s the dbmail setup within sql that’s corrupted or as Microsoft told me "stalled" are you sending HTML over the dbmail from say a job within sql using cast?
If so check the job and make sure there isn’t a problem inside first but what i did was delete the dbmail profile and then just re made it and then it just decided to start working again.
Have you also looked with the administrate tools as usually it will post an application error on why it failed (inside control panel)
Let me know if the deletion of the profile worked and i can maybe take you through a couple of things i was told to try first.
I have almost exactly this problem. I say, almost exactly because the answer that worked for this gentleman did nothing whatsoever for me. I can open my own database and see all of the lovely RS data sitting there staring at me but the actual Reporting Services installation still can't. This all came about because of precisely what he said. We accidentally left the password policy on on the Reporting Services account and it expired. When I changed it the whole thing went kaputt. I'm still getting the "key cannot be used in current state" error message even after dropping all encrypted data from the RS installation. I have no access to the Report Manager to reset encrypted information. Has anyone got any suggestions?
EDIT: In continuing my research I found this suggestion. It's not that.
Well... here's the thing.
I eventually tried creating a whole new user to take charge of the SSRS operations. I also remembered to update those details on our live data server. (I did this first and it failed to work as it was still telling me the key could not be used then.)
I guess that there must be something that prevents the reassignment of the SSRS gofer account's password. The new user is set up identically and works perfectly. So that's what cleared it up for me but I'm a little irritated that I still don't know exactly why...