June 25, 2017 at 5:31 pm
Saturday morning a job that was running suddenly stopped populating 1 of the columns, although the job kept running and updated the others columns. At the same time the column stopped populating, the Server Application Log shows this:
The column that didn't get updated is populated from a simple SQL function that encodes an int.
This process ran for years on our old server, but now on SQL 2016 we have had a few odd things. I applied SP1 a few months ago
Activation context generation failed for "C:\Program Files\Microsoft SQL Server\MSSQL13.MSSQLSERVER\R_SERVICES\Tcl\bin64\tk85.dll".Error in manifest or policy file "C:\Program Files\Microsoft SQL Server\MSSQL13.MSSQLSERVER\R_SERVICES\Tcl\bin64\tk85.dll" on line 9. The value "x64" of attribute "processorArchitecture" in element "assemblyIdentity" is invalid.
Source: SideBySide
Event ID: 63
June 27, 2017 at 6:18 pm
I am on SP1, but there are 3 Cumulatives Updates since SP1. I will install CU3 and hope it fixes the DLL problem.
I also have what seems to be a memory leak on a different SQL 2016 server, so just installed CU3 and hope that helps.
More problems with SQL 2016 in 3 months than with SQL 2005/2008 in years.
June 27, 2017 at 6:50 pm
homebrew01 - Tuesday, June 27, 2017 6:18 PMI am on SP1, but there are 3 Cumulatives Updates since SP1. I will install CU3 and hope it fixes the DLL problem.I also have what seems to be a memory leak on a different SQL 2016 server, so just installed CU3 and hope that helps.
More problems with SQL 2016 in 3 months than with SQL 2005/2008 in years.
Did you search on your first error at all? I just did and there are quite a few interesting posts - some same problems with R dll and then other apps in different posts.
Many mention Microsoft Visual C++ Redistributable version issues, some worked with a reinstall. Just a thought if the CU doesn't fix the issue.
Hope the upgrades stabilize for you soon...
Sue
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply