Service Update 10.0.38 Upgrade Errors

(1) Share

Report

Posted on by CU27040900-9

Hi,

I upgraded the env to 10.0.35 to 10.0.38, and there was no error during service update. I started to Full-Build the models. I got 2 errors on Application Suite.

The enumeration element 'Tls13' is not defined on type 'System.Net.SecurityProtocolType'.

Class:

AxClass_CatCXMLPunchoutHandler.xpp
AxClass_CatCXMLPurchRequestSend.xpp

How I can resolve these errors & will it create an issue/impact on Production and UATs Env as well if I apply the service update? Thanks.

I have the same question (0)

All responses (4)

Answers (3)

Sort by

Verified answer

Kevin Xia Microsoft Employee on at

Like
a
(1)

Report
Copy link

Link copied!

Hi,

There have been discussions about similar issues on the forums before, and you can refer to this old thread: Solved: Getting error during full build after Microsoft version upgrade from V36 to V38 (dynamics.com). As mentioned by other consultants, this element was added in .NET Framework 4.8, so you need to install it.

Best regards,

Kevin

Was this reply helpful? Yes No
Verified answer

Layan Jwei 8,239 Super User 2026 Season 1 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi,

You need to install.net framework 4.8

As the document below says "For TLS 1.3, target .NET Framework 4.8 or later"
And Tls13 enum relates to TLS 1.3 security protocol.

https://learn.microsoft.com/en-us/dotnet/framework/network-programming/tls

Thanks,

Layan Jweihan

Please mark this answer as "Verified" if it solved your issue. In order to help others who will face a similar issue in the future

Was this reply helpful? Yes No
CU27040900-9 11 on at

Like
a
(1)

Report
Copy link

Link copied!

Thanks for the answer. Will it going to create an issue on D365F&O Production & UAT's as well?

Was this reply helpful? Yes No
Verified answer

André Arnaud de Cal... 305,881 Super User 2026 Season 1 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi Community member,

It will not have an issue for Microsoft-managed production and UAT environments. In that case, Microsoft is updating all pre-requisites. In case of an on-premise deployment, you are responsible for keeping the related software, like the .Net version up to date.

Anyway, there is no need to build the standard application models. This was usually done to update cross references. There is now an option to update cross-references without running a full build.

Was this reply helpful? Yes No