Quantcast
Channel: Symantec Connect - Endpoint Management - Discussions
Viewing all articles
Browse latest Browse all 6689

Upgrade from SD 7.5 MP1 to SD 7.5 SP1 error in Incident Management Workflow

$
0
0
I need a solution

Dear All,

On upgrading from SD 7.5 MP1 to SD 7.5 SP1 (no errors detected in the WF 7.5 to WF 7.5 SP1 upgrade), the process finished and did not show any errors during the install. However, the following error was found in the upgrade log:

ERROR 11:38:59,573 4 Symantec.ServiceDesk.Installation.InstallSteps.RunModulePostInstallCodeStep - Post-installation step for module [Incident Management] failed: Could not load file or assembly 'Symantec.ServiceDesk.WebParts, Version=7.5.1622.1, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.
System.IO.FileNotFoundException: Could not load file or assembly 'Symantec.ServiceDesk.WebParts, Version=7.5.1622.1, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.
File name: 'Symantec.ServiceDesk.WebParts, Version=7.5.1622.1, Culture=neutral, PublicKeyToken=null'
   at Symantec.ServiceDesk.Module.Im.IncidentManagementModule.RegisterIncidentWebParts()
   at Symantec.ServiceDesk.Module.Im.IncidentManagementModule.OnAfterInstallation(InstallationContext args)
   at Symantec.ServiceDesk.Installation.InstallSteps.RunModulePostInstallCodeStep.DoExecute()

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

I cannot see anything wrong with the Workflow after running the upgrade. After upgrade all of the Assemblies are on 7.5.3000, however, I have found the Symantec.ServiceDesk.WebParts 7.5.1622.1 in:

C:\Program Files\Symantec\Workflow\ProcessManager\bin

and in:

C:\Windows\Microsoft.NET\Framework64\v2.0.50727\Temporary ASP.NET Files\processmanager\19185c1c\b58c041a\assembly\dl3\25d9b1bb\67fa285f_52face01

Which seems to suggest that the DLL is in the assembly cache. Since I *COULD* re-run the upgrade process again and log the process, it would take me a long time and therefore, I need to have a reason to do this, but it all seems to be working, and my questions are:

1) I cannot test EVERYTHING in the Incident Workflow and I am wondering what the upgrade has NOT done - what should I be looking for?

2) Does anyone know what might be causing this?

3) Do I go back and start again, because something is borken?

4) *WAS* anything broken?

Kindest regards,

QuietLeni


Viewing all articles
Browse latest Browse all 6689

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>