Closed YassinAbukar closed 2 months ago
Hi @YassinAbukar ,
Hi @vrosu ,
1) we are using the 4.1.0. 2) after running the service restartThing in gitHubThingworx no entry can be found in either applicationLog or scriptLog. oddly when we try to disable the thing we get the error message : Thing [gitHub Thingworx] is not running. and the thing stays enabled. 3) yes, on the other environments on which we are running 9.3.7-b1432 is working fine.
On the server where we are having problems we are running the 9.2.1-b112. can it be caused by a ghostEntity/value ?
Hi @YassinAbukar , I observed that at point 2 you mentioned the ApplicationLog and ScriptLog, but if you read my original question at point 2 I asked about another log file, ErrorLog and ScriptErrorLog files. Can you please send those? Another observation is that on point 3 you replied that the extension works fine on 9.3.7, but my question was if you used the extension as explained in the User Guide. The reason of my asking this is because, from time to time, I see customers creating manually the GitThing, or importing directly from another system, while the user guide requires you to use the User Interface (key here is to know that the act of opening the Main Mashup first time is doing certain critical settings.)
You'll see in the 4.1.0 User Guide two topics:
Summarizing -Please attach the log files I've asked about -Restarting the server - try and do it if possible, but I still would like to find out what's the cause of that error - that's why I'm asking about those log files.
Hi @YassinAbukar. Any news regarding this issue? Did you manage to solve it on your end?
Hi @vrosu , I apologize for the late response I didn't recive any notification. We've tried to restart the server but it didn't help. As for the version we are using. Dev Server : ThingWorx 9.2.1-b112 here`s the Error Log. ErrorLog.zip
On the other Environments (QA and Prod) we are currently using ThingWorx 9.3.7-b1432, and it`s working fine.
I do not see other error outside of "Thing [github2_thing] is not running ". If you can enable stacktracing for the logs and resend the ErrorLog.log after you try and save the file it might shed some light.
We are currently facing issues with the GitHub extension. Despite our attempts to resolve it, the problem persists.
We initially attempted to re-import the extension from our production server, which is functioning correctly, but unfortunately, the issue remains unresolved. Furthermore, creating a new instance did not yield any positive results.
here's a list of the errors we're getting.