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.
Yes, it runs successfully and this is what is killing me, it succeeds but login error is generated in error log.
I've seen this with the job syspolicy_purge_history job as well. It's notorious for knocking on the wrong door when you have multiple instaces, leaving login failures in the errorlog. But the job still reports success. And it is configure to report failure or errors (like most other jobs steps are).
But obviously the code of the job could have an error handler that traps the error and thinks "who cares?" and just drops it on the floor.
Yes, I have a the defauylt instance and a 2nd one on this server
And the error message appears on which of the two instances?
Onn the default where the job runs
So did you check the jobs on the other instance?
I monitor both error logs for default and named instance with the same powershell script and it populates a table, 1st column in this table is SQLInstance anme
The email/alert I receive from my script that runs every 1 hour indicates an error in the default instance as noted above, again here it is
OK, so if this error is logged on the default instance, I would guess comes from a job on the named instance. It could also be something that connects to the named instance and then tries to access the default instance over a linked server or similar, but look at the jobs on the named instances first.