SmartConnector Forum
Schneider Electric support forum about SmartConnector applications for integration of other building management systems (BMS) into EcoStruxure Building Operation.
Link copied. Please paste this link to share this article on your social media post.
Hi,
I am getting this error. Is it because the Assembly ID that is provided in the extension definition is different than the DLL's assembly ID?
Thank you.
Mike
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Hi,
We are using the release version of the extension DLL. Do we need to use the "Assembly Public Key Token" in order to create a valid license?
See below the error that we get:
2020-11-30 20:30:03.9943,Info,WorkerThread,<no principal>,EBO-OPC Client Setup Processor,Started,
2020-11-30 20:30:03.9943,Info,WorkerThread,<no principal>,EBO-OPC Client Update Processor,Started,
2020-11-30 20:30:03.9943,Status,Service,<no principal>,Attaching context listeners,
2020-11-30 20:30:04.0023,Debug,Service,<no principal>,Redirecting assembly load of Mongoose.Process, Version=2.4.10.0, Culture=neutral, PublicKeyToken=223885051a9a1eff, loaded by (unknown),
2020-11-30 20:30:04.0023,Debug,Service,<no principal>,Redirecting assembly load of Mongoose.Common, Version=2.4.10.0, Culture=neutral, PublicKeyToken=223885051a9a1eff, loaded by (unknown),
2020-11-30 20:30:04.0023,Debug,Service,<no principal>,Redirecting assembly load of Mongoose.Common, Version=2.4.10.0, Culture=neutral, PublicKeyToken=223885051a9a1eff, loaded by (unknown),
2020-11-30 20:30:04.1303,Debug,WorkerThread,<no principal>,EBO-OPC Client Update Processor,InstantiateProcessor,ET=136 mSec,
2020-11-30 20:30:04.1303,Debug,WorkerThread,<no principal>,EBO-OPC Client Setup Processor,InstantiateProcessor,ET=136 mSec,
2020-11-30 20:30:04.1543,Debug,WorkerThread,<no principal>,EBO-OPC Client Setup Processor,Execute (start),2020-11-30T18:30:03,
2020-11-30 20:30:04.1543,Debug,WorkerThread,<no principal>,EBO-OPC Client Update Processor,Execute (start),2020-11-30T18:30:03,
2020-11-30 20:30:04.1543,Debug,Processor,<no principal>,Processor EBO-OPC Client Update Processor Execute started,
2020-11-30 20:30:04.1543,Debug,Processor,<no principal>,Processor EBO-OPC Client Setup Processor Execute started,
2020-11-30 20:30:04.1703,Debug,Service,<no principal>,Redirecting assembly load of SxL.Common, Version=2.4.10.0, Culture=neutral, PublicKeyToken=223885051a9a1eff, loaded by (unknown),
2020-11-30 20:30:04.1703,Debug,Service,<no principal>,Redirecting assembly load of SxL.Common, Version=2.4.10.0, Culture=neutral, PublicKeyToken=223885051a9a1eff, loaded by (unknown),
2020-11-30 20:30:04.2103,Status,Service,<no principal>,Starting REST Providers,
2020-11-30 20:30:04.2823,Info,Processor,<no principal>,MayNotContinue: The license you are attempting to use is not for the referenced assembly.,
2020-11-30 20:30:04.2823,Info,Processor,<no principal>,MayNotContinue: The license you are attempting to use is not for the referenced assembly.,
2020-11-30 20:30:04.2823,Debug,WorkerThread,<no principal>,EBO-OPC Client Setup Processor,Execute (end),2020-11-30T18:30:03,ET=288 mSec,
2020-11-30 20:30:04.2823,Info,WorkerThread,<no principal>,EBO-OPC Client Setup Processor,Ended unsuccessfully,
2020-11-30 20:30:04.2823,Debug,WorkerThread,<no principal>,EBO-OPC Client Update Processor,Execute (end),2020-11-30T18:30:03,ET=288 mSec,
2020-11-30 20:30:04.2823,Info,WorkerThread,<no principal>,EBO-OPC Client Update Processor,Ended unsuccessfully,
Any idea?
Thank you.
Mike
Link copied. Please paste this link to share this article on your social media post.
HI Michael,
I suspect that you have not setup licensing correctly on your extension in Smart Connector Server.
When you create the extension in Smart Connector Server, the Assembly name should be your .dll name "MyCustomExtension.dll", and the Asembly ID should be the GUID in your extensions AssemblyInfo.cs (e.g. [assembly: Guid("1641be71-0674-4895-910d-f1f88082c20a")], this GUID should be there automatically, so just copy that GUID out.
Once you create the extension, open it in Smart Connector Server, you should see a populated "Public Key" field. Copy the value of this field, and added the following to your AssemblyInfo.cs file:
[assembly: PublicKey("YOURPUBLICKEYFROMSMARTCONNECTORSERVER")]
Then rebuild, and redeploy.
Best Regards,
-Jeff
Link copied. Please paste this link to share this article on your social media post.
Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.