Support
Home
Forums
Forge
Ideas
Community › Forums › Installation Troubleshooting

Could not load file or assembly "OutSystems.Common"

Community › Forums › Installation Troubleshooting

Could not load file or assembly "OutSystems.Common"

  
New Post
I hope this is the correct forum.  We have three OutSystems enviroments (Development, QA, and Production) with LifeTime.  We are now getting issues with our QA environment, in that when trying to go into ServiceStudio or Deploy via LifeTIme, we get the following error:

There was an error processing your request:
Could not load file or assembly 'OutSystems.Common, Version=8.0.1.23, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.
 
 
Could not load file or assembly 'OutSystems.Common, Version=8.0.1.23, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.
   at ssServiceCenter.RssExtensionOMLProcessor.MssActivationGetLicenseInformation(HeContext heContext, IRecord& outParamLicenceInformation)
   at ssServiceCenter.Actions.ActionActivation_UpdateSession(HeContext heContext)
   at ssServiceCenter.Actions.ActionOnBeginWebRequest(HeContext heContext)
   at ssServiceCenter.Flows.FlowCommon.ScrnGeneralReportError.Page_Load(Object sender, EventArgs e)
   at System.Web.UI.Control.OnLoad(EventArgs e)
   at System.Web.UI.Control.LoadRecursive()
   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

The applicatons that run on the QA server continue to run without error, but we cnnot access ServiceStudio, which means we cannot depoy any development apps to that server now.

The Production/LifeTime server is throwing the following error (which I believe is related):
Id:
9854ba0e-8bab-4d8d-8f52-89b91bf42689
Time of Log:
2015-04-06 05:01:43
eSpace:
LifeTimeEngine
Tenant:
ServiceCenter
User:
PlatformServices (3)
Session Id:
No session
Server:
AGILEWEBPROD07
Module:
Web Reference
Message:
Server was unable to process request. ---> LifeTime component not licensed.
Stack:
   at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
   at ssLifeTimeCore.WRefPlatformServices_v8_0_0.WRefPlatformServices_v8_0_0.Module_VersionExistsWithGeneralHash(String inWSUserName, Boolean inWSUserNameSpecified, String inWSPassword, Boolean inWSPasswordSpecified, WORCCS_ModuleVersionInfoRecord inWSModuleVersionInfo, Boolean inWSModuleVersionInfoSpecified, String inWSModuleVersionGeneralHash, Boolean inWSModuleVersionGeneralHashSpecified, Nullable`1& outWSVersionExists, String& outWSVersionHash)
-Env-
eSpaceVer: 4 (Id=82, PubId=165, CompiledWith=8.0.1.23)
RequestUrl: http://127.0.0.1/LifeTimeEngine/_TimerHandler.asmx (Method: POST)
AppDomain: /LM/W3SVC/1/ROOT/LifeTimeEngine-65-130727664708195000
FilePath: C:\...\PS\running\LifeTimeEngine.568277649\
Locale: en-US
DateFormat: yyyy-MM-dd
PID: 3836 ('w3wp', Started='3/31/2015 4:13:05 PM', Priv=343Mb, Virt=3477Mb)
TID: 128
Thread Name: 
.NET: 2.0.50727.5485

Any help in where to start resolving this issue would be GREATLY appreciated as we cannot deploy any fixes or new features into production until this is fixed.
Dislike(0)
Like(0)
Dislike(0)
Like(0)
Hi Steven,

Reach out to support to get help. Use the Submit Feedback button or use one of the contacts.
Dislike(0)
Like(0)
Dislike(0)
Like(0)
Login to reply
Company
Corporate Site
Contacts
Support
Technical Support
Community Forums
 OutSystems© All rights reserved. Custom built with (h) and (o)