The UTC time represented when the offset is applied must be between year 0 and 10,000
See original GitHub issueUsing a database from YAF 2.31 to update to the latest source. The upgrade goes fine, but after clicking “Finish”, this error occurs. I know I mentioned it in the Sample Application repo, but wanted to capture it with a little more detail for you. I’m not sure what key AdminPageAccess1 refers to, but that might help you.
Issue Analytics
- State:
- Created 2 years ago
- Comments:18 (18 by maintainers)
Top Results From Across the Web
The UTC time represented when the offset is applied must ...
The UTC time represented when the offset is applied must be between year 0 and 10,000. Parameter name: offset ... My view model...
Read more >The UTC time represented when the offset is applied must ...
HCW Error on the "Office 365" side - The UTC time represented when the offset is applied must be between year 0 and...
Read more >The UTC time represented when the offset is applied must ...
ArgumentOutOfRangeException: The UTC time represented when the offset is applied must be between year 0 and 10,000. (Parameter 'offset') #33673.
Read more >DateTimeOffset ArgumentOutOfRangeException error in ...
The ArgumentOutOfRangeException bug (The UTC time represented when the offset is applied must be between year 0 and 10,000) in ASP.
Read more >The UTC time represented when the offset is applied must ...
The UTC time represented when the offset is applied must be between year 0 and 10,000. Parameter name: offset ” ExceptionPath = Root...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Did you follow the upgrade guide? make sure you update the appsettings with the legacy provider info. Then you can login
I was able to reproduce the issue, and also resolve it.