Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

Date format in Windows 10 en-us/en-gb
Vizual
#1 Posted : Tuesday, September 5, 2017 5:07:59 AM(UTC)
Groups: Member
Joined: 9/5/2017(UTC)
Posts: 3
Location: uk

We are running an asp.net app (v4.0) and under all operating systems apart from windows 10 it works perfectly, but on Windows 10 the date format lists as en-us (as opposed to en-gb) - this causes an issue parsing the date.

If we run the webs server as an application under comparability mode (Win 8) it works fine too :-/ (though it would appear the service ignores any comparability mode settings so this isn't a solution)

If we run the web app on windows 10 under IIS it also works fine.

We have replicated this on a number of machines (all of which have Windows 10 creators edition loaded)

Has anyone else come across this or got any thoughts? Even if not i hope this post may save someone hours of work identifying the issue if they see it!

Regards

patrick
Ultidev Team
#2 Posted : Thursday, September 7, 2017 9:03:43 AM(UTC)
Ultidev Team

Groups: Administration
Joined: 11/3/2005(UTC)
Posts: 2,248

Thanks: 28 times
Was thanked: 55 time(s) in 54 post(s)
Hi,

We are sorry for the delayed reply. Could you please confirm that the issue is specific to the UWS and is absent when run under IIS/Espress?

Vest regards,
UltiDev Team.
Please donate at http://www.ultidev.com/products/Donate.aspx to help us improve our products.
Vizual
#3 Posted : Thursday, September 7, 2017 10:04:59 AM(UTC)
Groups: Member
Joined: 9/5/2017(UTC)
Posts: 3
Location: uk

Yes, under IIS its fine and if we run UWS as an application in compatibility mode (Windows 8) its also fine.

As summary, same application/database in all cases

Windows 8 - no problems
Windows 10 in UWS in Windows 8 compatability mode - no problems
Windows 10 native mode IIS - no problems
Windows 10 native mode UWS (or service) - problems


We inserted logging in the App/handlers and we can see the nationality code change....on the same machine in and out of compatibility mode, similarly IIS on the same machine no problems.

We have replicated on more than one Windows 10 machine, but they ARE all running creators edition (not sure if that's significant or not!), but i would suspect it may be as I would be amazed if we hadn't run this same function on a previous build of Windows 10 under UWS, but I cant guarantee that....
Ultidev Team
#4 Posted : Tuesday, September 12, 2017 8:47:37 AM(UTC)
Ultidev Team

Groups: Administration
Joined: 11/3/2005(UTC)
Posts: 2,248

Thanks: 28 times
Was thanked: 55 time(s) in 54 post(s)
Hi there!

We are sorry again - we're in the area affected by the hurricane Irma and are still dealing with issues related to power outages.

Assuming that application host process is running under LOCAL SYSTEM or NETWORK SERVICE accounts, this article could be helpful: https://stackoverflow.com/a/26474273/516508. It describes similar situation where culture settings for a non-interactive user are not set properly. It says LOCAL SYSTEM account culture is set in "HKEY_USERS/.DEFAULT/Control Panel/International" registry key.

Best regards,
UltiDev Team.
Please donate at http://www.ultidev.com/products/Donate.aspx to help us improve our products.
Vizual
#5 Posted : Thursday, September 14, 2017 9:05:49 AM(UTC)
Groups: Member
Joined: 9/5/2017(UTC)
Posts: 3
Location: uk

Hi I think we have solved this!

Essentially it seems to be down to the way Windows 10 delivers the country information (that differs in compatibility mode) - we assume a shim is applied to use a different method.

If the machine has been built in US format originally (as per anything from Dell etc!) the service account country code are set to US and UWS picks this up.

In order to fix this :

Control panel/ time and language/region and language/ additional date, time, & regional settings/region/administrative tab/copy settings button/tick all options/ OK

This copies the regional settings from the current account to ALL other accounts....

Reboot machine

We would assume this might affect anyone who is running in non US date format.

As IIS doesn't seem to suffer the same fate we assume Microsoft either use a different method originally, or have silently fixed the issue in IIS.

Hope this adds to the collective knowledge and saves someone else some head scratching!
Ultidev Team
#6 Posted : Thursday, September 14, 2017 11:57:39 AM(UTC)
Ultidev Team

Groups: Administration
Joined: 11/3/2005(UTC)
Posts: 2,248

Thanks: 28 times
Was thanked: 55 time(s) in 54 post(s)
We highly appreciate your sharing this insight with the community!

All the best,
UltiDev Team.
Please donate at http://www.ultidev.com/products/Donate.aspx to help us improve our products.
Rss Feed  Atom Feed
Users browsing this topic
Guest
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You can vote in polls in this forum.