|
It's an environement problem from what I checked but anyway : I've got scripts doing heavy lifting between Ax2012 instances (PRD-> DEV, TRN, SBX, yada yada) These fuckers have stopped working properly, and when looking for what caused this I found that it was it was a simple smo $Scripter.EnumScript($Object)) which stopped working. A simple script like https://pastebin.com/1kvB7xgz will work perfectly against a certain SQL server , and will fail miserably against the dev server even in local (using the same AD user btw.) The error : C:\Users\xxx\.Desktop\test.ps1 : TRAPPED: Microsoft.SqlServer.Management.Smo.FailedOperationException + CategoryInfo : NotSpecified: (  [Write-Error], WriteErrorException+ FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,test.ps1 C:\Users\xxx\Desktop\test.ps1 : TRAPPED: Script failed for Table 'dbo.SYSSERVERCONFIG'. + CategoryInfo : NotSpecified: ( [Write-Error], WriteErrorException+ FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,test.ps1 Exception calling "EnumScript" with "1" argument(s): "Script failed for Table 'dbo.SYSSERVERCONFIG'. " At C:\Users\axservices\Desktop\test.ps1:49 char:20 + foreach ($s in $Scripter.EnumScript($Object)) + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: ( [], ParentContainsErrorRecordException+ FullyQualifiedErrorId : FailedOperationException SQL Server rebooted, no right on the account have been modified,.. I'm lost. Anyone ever seen something like this ? Edit : solved by recent kbs uninstallation. Picardy Beet fucked around with this message at 08:58 on Dec 6, 2018 |
#
?
Dec 5, 2018 13:53
|
|
|
|
| # ? May 6, 2024 21:41 |
|