Dear Community User! We have started the migration process.
This community is now in READ ONLY mode.
Read more: Important information on the platform change.

cancel
Showing results for 
Search instead for 
Did you mean: 
SOLVED

C# SDK Apps return error/exit code 127

C# SDK Apps return error/exit code 127

schoeffler
Member

Hi all,

not sure if I missed something obvious. When I build the C# .NET apps from the SDK, upload&install them on a virtual ctrlX (via ctrlX Works), they are not started.

For example building and running the diagnosis example (https://github.com/boschrexroth/ctrlx-automation-sdk/tree/main/samples-net/diagnostics.logbook) does not result in lookbook entries. Having a look into the logs, shows me that the diagnosis.logbook application can not be found:

schoeffler_0-1645712018233.png

From the first look, the file location looks alright:

schoeffler_1-1645712088071.png

I tried out some other C# example apps where I got the same issue. Another developer tried to follow the C# SDK as described and ran exactly in the same issue.

Operating system: Ubuntu Core 20
Architecture: amd64

ctrlX Works version 1.12.0

ctrlX SDK version: 1.12.1

2 REPLIES 2

nickH
Community Moderator
Community Moderator

Hello,

I tried to reproduce your problem, but the C# .NET examples work like expected for me. Here the logbook example:

2022-02-25_09h43_47.png

I used the preconfigured QEMU in the SDK V1.12.1(tested it also with 1.12.0) as development environment. In the development environment I ran the included install-dotnet-sdk.sh and install-snapcraft.sh scripts. 

ctrlX Works version: 1.12.2 (tested it also with 1.12.4)

ctrlX COREvirtual Base image version: 1.12.5 (tested also with 1.12.2 and 1.12.6)

2022-02-25_08h38_22.png

 

The location of your snap looks good and is similar to mine.

 

Thanks for checking!

We were able to solve the problem: We noticed that the problem occurs only with snaps that were build by one specific machine (Development qemu). After a full reinstall of the dotnet SDK 6.0, also snaps from this machine did work. We are almost 100% sure it had something to do with a wrong/incompatible dotnet version.

// Unfortunately, I can't tell how we installed the previous "incompatible" dotnet SDK (it was dotnet v5), since we did the reinstall at the very beginning.

Icon--AD-black-48x48Icon--address-consumer-data-black-48x48Icon--appointment-black-48x48Icon--back-left-black-48x48Icon--calendar-black-48x48Icon--center-alignedIcon--Checkbox-checkIcon--clock-black-48x48Icon--close-black-48x48Icon--compare-black-48x48Icon--confirmation-black-48x48Icon--dealer-details-black-48x48Icon--delete-black-48x48Icon--delivery-black-48x48Icon--down-black-48x48Icon--download-black-48x48Ic-OverlayAlertIcon--externallink-black-48x48Icon-Filledforward-right_adjustedIcon--grid-view-black-48x48IC_gd_Check-Circle170821_Icons_Community170823_Bosch_Icons170823_Bosch_Icons170821_Icons_CommunityIC-logout170821_Icons_Community170825_Bosch_Icons170821_Icons_CommunityIC-shopping-cart2170821_Icons_CommunityIC-upIC_UserIcon--imageIcon--info-i-black-48x48Icon--left-alignedIcon--Less-minimize-black-48x48Icon-FilledIcon--List-Check-grennIcon--List-Check-blackIcon--List-Cross-blackIcon--list-view-mobile-black-48x48Icon--list-view-black-48x48Icon--More-Maximize-black-48x48Icon--my-product-black-48x48Icon--newsletter-black-48x48Icon--payment-black-48x48Icon--print-black-48x48Icon--promotion-black-48x48Icon--registration-black-48x48Icon--Reset-black-48x48Icon--right-alignedshare-circle1Icon--share-black-48x48Icon--shopping-bag-black-48x48Icon-shopping-cartIcon--start-play-black-48x48Icon--store-locator-black-48x48Ic-OverlayAlertIcon--summary-black-48x48tumblrIcon-FilledvineIc-OverlayAlertwhishlist