I am having an issue with the error logging in our development SharePoint 2010 box. This is a new install. When working on an application page, I had an error and went to the logs. Pretty much every other thing in the world is in the logs except for my error(s). I looked for the correlation ID and time and nada.
I've followed tutorials on how to configure the diagnostic logging. This is similar to another StackOverflow post, however the solution isn't working for me and I'm trying ti revive the thread. We have a stanging machine that I was working on until the dev machine was up and the logging worked fine there. I used that as an example and set the SharePoint Foundation and SharePoint Server categories to Error and Medium (I've even set them both to Verbose) with no result.
Anyone else have an issue with this?
I figured out the problem. Someone told me to make sure the SP webapplication AppPool account is part of the "Performance Log Users" group. After much back-and-forth, I checked the Performance Log Users group and it was EMPTY! I put in my AppPool service account and farm account into that group and also I had to assign the "Log on as a batch job" user right to the Performance Log Users group. It's been logging ever since. :-)
Related
On Monday I messed up with a database.
We have an application running on a VPS, using cPanel and phpmyadmin, and I informed the developers I will be doing some queries on the DB to extract information.
So, I did a few large queries using the "Visual Builder" query tool and the web-application got stuck. The queries weren't loading and even refreshing the page did not work. The website wasn't loading and users couldn't log in. So I used WHM to log in as root and kill the queries manually. After I did this, the system was still not running.
Then, the database completely freaked out and I got these error messages:
After doing this, the DB somehow fixed itself and the web application was working again. However, we saw that we could not update some jobs or add new jobs in the system. If you pressed the "SAVE" button on a job, the system just gave an "undefined" message.
The developers had a look and discovered this was causing the issue:
[
The devs went ahead and added the definer and the issue was resolved. The blacked out "user"#1.0.0.0" is the actual cPanel account username.
However, this did not last as yesterday evening the exact same situation was occurring. The web-application was running fine on Tuesday and most of Wednesday, then all of a sudden users couldn't update their jobs again which means the definer user was removed once again even though nobody did anything in the database.
Has anyone encountered this issue before? I read this thread on the topic and even though what they say makes sense, I believe the developers did this but the error still occurred.
When I log into phpmyadmin via cPanel, I get a weird user called "cpses_234ikjih#localhost.com". Does this perhaps have something to do with this error? I believe before the server went crazy, this user was only the name of the cPanel account (for example: "cPanelAccountName#localhost.com".
To summarize your post, what I'm seeing is that you have a MySQL user, the user disappeared, you recreated the user, and it went away again.
There must be some external factor here. Someone could have access to your database and is deleting the user maliciously or out of misunderstanding, there could be a scheduled job, or it could be something to do with your web host.
I'd start by auditing the database accounts, and restricting access as much as possible. Check any interface that's exposed to the web, such as WordPress, Joomla, or other applications.
You should enable logging, there are several degrees of logging that MySQL can allow. I think the most useful for you would be the audit log, although honestly I've never used that specifically. You'd enable that to log future events. The binary log may contain record of what has already occurred.
SOLVED
I managed to solve this by changing MySQL database password and cPanel account password.
I read one post by someone saying that there was a session file which perhaps stored an old session and that changing passwords could resolve this. Luckily it did, have not had the error 1449 appearing for 5 days now.
I'm trying to access an Azure SQL database of mine from SQL Server Management Studio on my local machine and have failed due to requiring 2FA. That's fine, I'll try and sort that.
What concerns me is the server that it's attempting to connect to. What the hell is "database.usgovcloudapi.net"???
I think the error is happened when you're using Active Directory Authentication to login your Azure SQL database.
The AD document Authentication and authorization error codes show us the error code and message, but doesn't tell us how to solve the problem:
You need call your AD administrator to re-configure your AD account and try again.
If you still have the error, the document suggest us:
Have a question or can't find what you're looking for? Create a
GitHub issue or see Support and help options for developers to learn
about other ways you can get help and support.
Update:
Congratulations that ataraxia has solved the error:
"Thank you, I got around it by changing the authentication provider to "Active Directory - Universal with MFA Support" on the SSMS login prompt, which then opened a browser window with the regular Microsoft online login and after entering my credentials sent a notification to my mobile, then returned to SSMS and authenticated."
If anyone want details about this, please #ataraxia in the comment.
Hope this helps.
That would be the Azure Government services, designed for use by US government agencies and their partners.
https://azure.microsoft.com/en-us/global-infrastructure/government/
When creating a new MVC app and clicking "change authentication".
After choosing "multiple organisations" clicking finish and logging in with my Microsoft account (the one used for Azure) I receive the following error:
User credential verification failed.
Error: Value cannot be null.
Parameter name: entity
Any ideas?
The error is very generic so has proved tricky to find a hint of what to try next.
EDIT:
I have remembered that I have Update 2 RC installed, so it's possible it's just a bug in the pre release.
Ok, I believe I have the answer to the issue.. Seems like this login dialog lets you log in using the Azure AD accounts, but also using Microsoft's accounts. And if you log in using the Microsoft account, it will give this error (even if this MS account has full access to your Azure account).
The solution is to go to the Active Directory in Azure and create a brand new account, mark it as a Global Administrator, then use that to log in when prompted in Visual Studio.
Microsoft has a write-up on the issue, describing the steps to go around it here:
http://www.cloudidentity.com/blog/2013/12/11/setting-up-an-asp-net-project-with-organizational-authentication-requires-an-organizational-account/
Restart VS. So that you wont get the same error again and clears the logged in user. You would need a user with Global Admin Rights in your Azure AD to login again.
How to log all sharepoint errors, workflow errors, custom code errors into one central place?
is it even possible?
SharePoint uses the ULS logs to do this. Have a look at the ULS Log Viewer for a utility that lets you easily view them. Also, you can write to the ULS logs in you custom code for any tracing you might wish to do.
The settings for what SharePoint is going to log to the ULS (trace log) and Event Log can be found in Central Administration: Monitoring - Configure diagnostic logging (http://xxxxxxx/_admin/metrics.aspx). This page also allows you to configure where the logs are stored. Note that in a farm, each server will have its own logs. You need to take this into consideration when diagnosing a problem.
The logs are written by the Windows Service 'SharePoint 2010 Tracing'. Often times when a user encounters an error in the SharePoint UI, they are given a 'Correlation ID' in the error message. This is a guid that can be searched for in the ULS logs. Note that this guid can take a few minutes to show up in the logs.
If you are developer then you can leverage to write all errors to ULS Logs ( where SP writes for all OOTB features )
http://sharepointnadeem.blogspot.com/2011/10/sharepoint-2010-diagnostic-logging.html
I've been developing a winforms app tied to sql server. I haven't rebooted in a while. Today i rebooted and now I can't log into sql. I used every account I know and their passwords including one that was working just before i rebooted and i get a 'Login failed' . I did take the database I use offline just before starting and I do have backups before then.
thoughts on what happened? Is there a way to bring the database back online OR somehow find out what passwords are? I even tried using windows authenication with me as an admin on the box AND sa (Yes, bad) and still no dice.
:-/ That's a rough place to be ... I wish you luck. Check out this blog post, not sure if you're using sql 2k5 or not, but if so, it may be helpful:
http://blogs.msdn.com/raulga/archive/2007/07/12/disaster-recovery-what-to-do-when-the-sa-account-password-is-lost-in-sql-server-2005.aspx
Have you checked to make sure that the service is actually running? Also are you trying to connect using IPC, TCPIP or named pipes? Whichever way make sure it's enabled in the configuration tools.
Since admin's on the box are SQL admins the only thing I can think of is that the service is not running.