I can't generate the Trial Balance Report in my production environment but it works in our pilot environment

I get this error in System Monitor when I try to generate a report:

Program Ice.Services.Lib.RunTask raised an unexpected exception with the following message: RunTask: Unable to load assembly Erp.Internal.GL.TrialBalance.dll for task 10385 or it contained no types that implemented the RunProcess method.
Stack Trace:
   at Ice.Hosting.TaskCaller.InnerExecuteTask(IceDataContext newContext) in C:\_Releases\ICE\RL3.2.200.0\Source\Framework\Epicor.Ice\Hosting\TaskCaller\TaskCaller.cs:line 121
   at Ice.Hosting.TaskCaller.ExecuteTask() in C:\_Releases\ICE\RL3.2.200.0\Source\Framework\Epicor.Ice\Hosting\TaskCaller\TaskCaller.cs:line 57
   at Ice.Lib.RunTask.BpmFriendlyTaskLauncher.Run(String sessionIdPrefix, IceContext db, Action taskRunner) in C:\_Releases\ICE\ICE3.2.200.9\Source\Server\Services\Lib\RunTask\BpmFriendlyTaskLauncher.cs:line 63
   at Ice.Services.Lib.RunTaskSvc.InnerRunTask(Int64 ipTaskNum, Boolean suppressTransaction) in C:\_Releases\ICE\ICE3.2.200.9\Source\Server\Services\Lib\RunTask\RunTask.cs:line 549

Also, when I go into the SSRS and I enter my GUID for the occurence, I get this error only in my production environment:

  • Échec de l’exécution de la requête pour le dataset ‘Company’. (rsErrorExecutingCommand) (Error executing the request for dataset Company)

What could cause this ? Is there a configuration missing somewhere ?

Thanks

Does that dll live in the client folder?

Sike, it should exist on the App server under Server>Assemblies, do you see it there

Yes, the dll is in Server > Assemblies. I looked and there is a lot of report that don’t work so we think that something went wrong with most dll. I guess a regeneration (if it’s possible) of the dlls would be the right thing to do.

Is the report a copy from the Pilot Env.?
If so, then the SharedReportDataSource might still be pointing to the Pilot one and not the live one.

probably re-importing the SSRS in your live environment could help…

Finally, we redeployed the custom dll (client and server) with the scripts under _Scripts_Client and _Scripts\Server and we recycled appPool and it worked.

Nobody knows what happened