This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(64, 19%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESE%3C/text%3E%3C/svg%3E)
On a sql 2k16, when I go through error logs, I find a lot of messages las follows
Server Date Process Count Text
SQL2K12 2021-03-15 13:30:44.640 spid17s 1 AppDomain 39 (MDS.mds_schema_user[runtime].38) unloaded.
SQL2K12 2021-03-15 13:00:15.550 spid62 1 AppDomain 40 (master.sys[runtime].39) created.
SQL2K12 2021-03-15 13:00:15.550 spid62 1 AppDomain 40 (master.sys[runtime].39) created.
SQL2K12 2021-03-15 10:00:43.090 spid45s 1 AppDomain 39 (MDS.mds_schema_user[runtime].38) created.
Not sure what this appDomain creating and unloading?
Thanks
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(67.2, 1%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETP%3C/text%3E%3C/svg%3E)
That is completely normal and expected when you are running MDS.
Correct, here is the right snapshot, it is "NT Service\SQLSERVERAGENT" account and this is there since the setup of SQL 4 or 5 years ago, never touched it
So that is where the SQLK12$ user is coming from.
Reminds to find out why BizTalk starts this job every five minutes.
Agree, but as I said earlier in a snapshot, job is disabled. In this case, why it is not able to find the login and always saying
"Reason: Could not find a login matching the name provided"
what does this mean?
It means what it says.
In your initial post you talk about an SQL 2016 instance, so I take it that this job is defined on an SQL 2012 instance, but for some reason knocks on the door to the SQL 2016.
Sorry, I don't know your environment. I only as much as you tell me, and it is not always easy to piece the things together.
Have you checked BizTalk yet?
Sorry for this, the server when was setup initially with SQL2K12, I named the server SQL2K12 but it has been migrated around 2017 to to 2K16 but I kept the name sql2k12, didn't change it
By the way, have you check Task Scheduler? There could be something hiding there.
Except 1 task I have done recently reading error logs and populate a table in 1 database, I am not aware of any other task.
However, while I was searching before responding, I found a 2 very strange tasks in a directory called XBLGameSave.
How those were schedueled and installed Xbox related stuff !!!!! This a server not win 10, any idea?
I have no idea of what that Xbox thing could be. I don't think it's related to SQL Server. :-)
Going back to that Agent job, did you check the job history?