Authorization failed only for my 7 year old A-10C (my A-10C II and all other modules work)

[Tom Kazansky]

Today I allways get an Authorization failure ONLY(!) for my 7 year old A-10C (my A-10C II and all other modules work).

I have bought it on Steam 2016 and transfered it as this was possible those days. I had never ever connected my Steam account to ED. Wasn't needed.

Is this a known issue?

 

edit:

I still get this error message on each start of DCS but what is odd: the time the authorization is valid is allways(!) 2d 23h 59m, I mean, If the authorization had failed before (earlier today), shouldn't this countdown show much less hours than allways start from 24h?

edit2: I'm using the Stable, Standalone Version od DCS, error occurs at ST nad MT

Edited August 31, 2023 by Tom Kazansky

[MAXsenna]

Today I allways get an Authorization failure ONLY(!) for my 7 year old A-10C (my A-10C II and all other modules work).
I have bought it on Steam 2016 and transfered it as this was possible those days. I had never ever connected my Steam account to ED. Wasn't needed.
Is this a known issue?
 
edit:
I still get this error message on each start of DCS but what is odd: the time the authorization is valid is allways(!) 2d 23h 59m, I mean, If the authorization had failed before (earlier today), shouldn't this countdown show much less hours than allways start from 24h?

When did you last re-confirm your Steam account in the ED Shop?

Sent from my MAR-LX1A using Tapatalk

[Tom Kazansky]

44 minutes ago, MAXsenna said:

When did you last re-confirm your Steam account in the ED Shop?

Sent from my MAR-LX1A using Tapatalk
 

Thanks for your help.

I never confirmed or re-confirmed my Steam account to the ED shop. It was not necessary for the last 7 years.

I bought the A-10C in 2016 and it was transfered to the Standalone DCS in 2017, before we had to link the Steam account to ED for modules like Mirage 2000C and later.

BigNewy stated here:

"Again, this only affects the M-2000C and future Steam DLC projects. It does NOT affect any existing sales. For example: past and future purchases of A-10C, FC3, F-15C, etc, are not affected by this."

btw. my FC3 also works, and was bought before my A-10C.

 

 

[MAXsenna]

Thanks for your help.
I never confirmed or re-confirmed my Steam account to the ED shop. It was not necessary for the last 7 years.
I bought the A-10C in 2016 and it was transfered to the Standalone DCS in 2017, before we had to link the Steam account to ED for modules like Mirage 2000C and later.
BigNewy stated here:
"Again, this only affects the M-2000C and future Steam DLC projects. It does NOT affect any existing sales. For example: past and future purchases of A-10C, FC3, F-15C, etc, are not affected by this."
btw. my FC3 also works, and was bought before my A-10C.
 
 

I just heard that some people had to do it after that authorization issue when Sinaï was released. I also only have one, the Ka-50, Steam module, but didn't noticed because I have two of that one, one from the ED store as well when they had a sale with all the four helicopters (at the time),
For fun I checked my validation, and it said that my Steam account was not linked anymore. Better safe than sorry and just check it to confirm everything is correct perhaps?

Cheers!

Sent from my MAR-LX1A using Tapatalk

[Tom Kazansky]

32 minutes ago, MAXsenna said:

I just heard that some people had to do it after that authorization issue when Sinaï was released. I also only have one, the Ka-50, Steam module, but didn't noticed because I have two of that one, one from the ED store as well when they had a sale with all the four helicopters (at the time),
For fun I checked my validation, and it said that my Steam account was not linked anymore. Better safe than sorry and just check it to confirm everything is correct perhaps?

Cheers!

Sent from my MAR-LX1A using Tapatalk
 

Guess I'll wait one or two days. Maybe it's just a server issue. After that I'll decide if I link my accounts or open a ticket.

What I don't get is, why are my Ka-50 BS2, my FC3 and F-5E are not affected and why does the time period always start at 24h on each start. There must be something going wrong. I can't believe this is the way it is meant to be.

Thank you anyway.

[Tom Kazansky]

@BIGNEWY

hi,

this issue still exists, is it perhaps connected to the server maintenance from Aug 28th?

Am I the only one reporting such an issue?

Could you please give me a clue how to get rid of this?

(as said above: it only affects my A-10C, not my A-10C II and not my FC3, F-5E and BS2 that I also bought on Steam in 2016 - before the Starforce-changes in 2017)

 

edit: here is the error message (in German) that shows 23h 59m at each start and that the A-10C is the only module affected:

Edited August 31, 2023 by Tom Kazansky

[BIGNEWY]

please contact support directly here they will assist you 

https://www.digitalcombatsimulator.com/en/support/

It is worth checking antivirus has not created a problem also

[Tom Kazansky]

1 hour ago, BIGNEWY said:

please contact support directly here they will assist you 

https://www.digitalcombatsimulator.com/en/support/

It is worth checking antivirus has not created a problem also

thanks @BIGNEWY !!!

it had something to do with the AVIRA antivirus. Crazy enough, I only had to disable it for exactly one start of DCS and the error message was gone.

Just for testing and against all what I know, I turned antivirus protection on again, and the issue was still gone.

well, again you are my Hero of the day BN! Big thanks!