SQLServer 2016 SqlServer Logs showing continuous Process ID xxxx was killed by hostname xxxxxxxx, host process ID xxxxx.
Spun up a new 2016 Sql Server and migrated a Solidworks PDM Professional database to the new server 1 week ago, Since then the workstations that are running the PDM clients keep showing up in the sql server log files with: Process ID xxxx was killed by hostname xxxxxxxx, host process ID xxxxx.
How can i troubleshoot this as i'd like to see the process that is killing the other process, so i can figure out what is going on.
Thank you in advance.
How can i troubleshoot this as i'd like to see the process that is killing the other process, so i can figure out what is going on.
Thank you in advance.
ASKER
Microsoft SQL Server 2016 (SP2-GDR) (KB4532097) - 13.0.5102.14 (X64) Dec 31 2019 22:39:35 Copyright (c) Microsoft Corporation Standard Edition (64-bit) on Windows Server 2016 Standard 10.0 <X64> (Build 14393: ) (Hypervisor)
Don't believe any SPs or CU's were installed (the previous system admin is no longer with us)
remote query timeout = 0
Don't believe any SPs or CU's were installed (the previous system admin is no longer with us)
remote query timeout = 0
Your SQL Server has SP2 + GDR (KB4532097) lsecurity patch installed so is not running just RTM and is safe.
Also looks like the execution times are set to unlimited which means SQL is not terminating processes because of that reason.
However...all these should be checked for each of the PDM clients matching the actual name from the "hostname xxxxxxxx" message - right?
And most important question is did you actually migrated the database to new server as described here https://www.cati.com/blog/2019/08/how-to-relocate-solidworks-pdm-to-a-new-server/
and were all the clients updated with new names?
Also looks like the execution times are set to unlimited which means SQL is not terminating processes because of that reason.
However...all these should be checked for each of the PDM clients matching the actual name from the "hostname xxxxxxxx" message - right?
And most important question is did you actually migrated the database to new server as described here https://www.cati.com/blog/2019/08/how-to-relocate-solidworks-pdm-to-a-new-server/
and were all the clients updated with new names?
ASKER
i followed all the steps in the article and pdm has been working for 2 weeks. I have isolated the kill commands to when they are navigating in windows explorer and double clicking on a directory, that is when the kill in sql is happening. it also happens when they start a search in the new search in this directory and they use the X to stop the search.
i am unsure what you are asking for this question: "However...all these should be checked for each of the PDM clients matching the actual name from the "hostname xxxxxxxx" message - right?"
i am unsure what you are asking for this question: "However...all these should be checked for each of the PDM clients matching the actual name from the "hostname xxxxxxxx" message - right?"
I meant to check if SQL was patched and remote query timeout = 0 on all the PDM clients - sorry for that.
From what you're describing above it may be that some permissions are missing or maybe not propagated properly or...broken by some patch/event that happened after those two weeks. Is it possible to see if anything significant changed in the environment at about the same time when these kill's started to occur?
From what you're describing above it may be that some permissions are missing or maybe not propagated properly or...broken by some patch/event that happened after those two weeks. Is it possible to see if anything significant changed in the environment at about the same time when these kill's started to occur?
ASKER
All the workstations were completely wiped and loaded with fresh windows 10 during the migration on the weekend of the 21st.
The kill commands started since we went live on the 23rd. I am not seeing any problems with functionality, just getting all these kill commands.
The kill commands started since we went live on the 23rd. I am not seeing any problems with functionality, just getting all these kill commands.
ASKER
solidworks confirms that this is working as designed.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Did you applied any SP's like SP2 and/or CU's on the new SQL 2016 installation?
Could you please check what is the "Remote Query Timeout" under SQL Server properties?