Activation on Windows 2019 Server

[PotatoCarl]

Hi

I installed all three Affinity Apps on Windows 2019 Server. I had to install them as Administrator. I can activate them as Administrator.

However, when I start them as User, I get "Please Try Again" each time I enter my credentials.

How can I make them usable for my user account?

Thank you.

[Dan C]

Hi @PotatoCarl,

As you are installing the apps on Windows Server 2019, it sounds as though this may be for a business or education licence.

Please email corpsupport@serif.com (for business) or edusupport@serif.com (for education) and our team will be happy to assist further.

Many thanks in advance

[PotatoCarl]

Actually it is not, as I use Windows Server for security and practial reasons (i.e. no forced updates) and prefer the Server versions to the "private".

As I am running linux on my main machine, I virtualize the Windows Host to be able to access a few selected Windows apps I need.

[Dan C]

Thanks for confirming that for me - this certainly isn't an environment we've directly tested, although technically should be compatible.

I'd like to request a Connection Checker report, as this may have more information as to the cause of this error. Please open the app, then from the licensing dialog, right-click anywhere and choose “Check connectivity…”.

This will generate a report, which can be attached to your reply here. Many thanks once again!

[walt.farrell]

It might also be useful to know:

• whether the MSIX- or EXE-based installers are being used.
• more exact Windows version information, e.g., from the winver command or from Settings > System > About.

[PotatoCarl]

When I try the "Connectivity Test" it shows the popup but nothing happens (as user). The windows cannot be closed, only via Task Manager

However, when I use the links of the FAQ in a browser (as user), the pages load without problem.

The system is:

Windows Windows Server 2019 Standard, Version 10.0.17763 Build 17763

Now, one strange thing happens: When I start any app as Adminsitrator it loads, then I close it and quickly start the same app as user it also starts. If I start a different Affinity app, the activation screen pops up.

[walt.farrell]

18 minutes ago, PotatoCarl said:

Now, one strange thing happens: When I start any app as Adminsitrator it loads, then I close it and quickly start the same app as user it also starts. If I start a different Affinity app, the activation screen pops up.

You would get something similar if you have a mix of the MSIX-based and the EXE-based applications installed.

20 minutes ago, PotatoCarl said:

Windows Windows Server 2019 Standard, Version 10.0.17763 Build 17763

You need build 19041 or later, I think 

[PotatoCarl]

17763 is the most current build for Windows Server 2019

 

https://learn.microsoft.com/de-de/windows-server/get-started/windows-server-release-info

[Dan C]

2 hours ago, PotatoCarl said:

When I try the "Connectivity Test" it shows the popup but nothing happens (as user). The windows cannot be closed, only via Task Manager

That's certainly interesting, thanks for trying that for me - does the 'Checking Connectivity' window appear, but not complete - or does this window not appear at all?

Can you please provide a screenshot of the exact error message you're seeing when trying to Activate the license?

Can you please also open Windows Run (Windows Key + R) and paste the following string, then press OK:

%appdata%\Affinity\

In the folder that opens, do you see a folder for each Affinity app (Photo/Designer/Publisher)? If so, please open one of these folders, you should see a '2.0' folder within this.

Please select the folder and rename this to '2.0_old' and then repeat for the other Affinity apps.

Now, try launching the apps again and activating - does this work now please?

2 hours ago, walt.farrell said:

2 hours ago, PotatoCarl said:

Windows Windows Server 2019 Standard, Version 10.0.17763 Build 17763

You need build 19041 or later, I think 

Build 17763 of Windows Server 2019 is Version 1809, which is compatible with Affinity V2.1 and above.
(there are some differences between Windows 10/11 and Windows Server that allows us to support the 'older' version of Windows Server, when compared to the regular OS versions - which do require build 19041 or later)

[PotatoCarl]

Please see the screenshots below.

When I rename the 2.0 folder and start an app the first time, I agree to the licenses and he asks me to import data from version 1. I say yes, the programm closes.

When I restart, the activation windows appears. I enter my ID -> "Please try again".

Connecrtivity Check -> See screenshot.

So, back to square one for me.

[Dan C]

1 hour ago, PotatoCarl said:

When I rename the 2.0 folder and start an app the first time, I agree to the licenses and he asks me to import data from version 1. I say yes, the programm closes.

Thanks for trying that - this sounds like the app is initially accepting your activation ID and opening - then during the V1 transfer process, the app crashes and potentially invalidates the local licensing file.

Can you please upload a copy of the new '2.0' folder generated from the above location, for the app that has opened and then crashed during V1 transfer?

Secondly, can you please follow the steps again to regenerate new versions of these '2.0' folders, then launch the Affinity apps, activate your license but select No to the V1 transfer prompt.

Do you find you're now able to license all 3 Affinity apps, and use these without crashing/being re-prompted to activate? (albeit, without your V1 data transferred).

[PotatoCarl]

Okay. when I do NOT select to import Version 1, it starts, however, it closes again after a few seconds.

One of the programs (publisher) does not have a connection to the account  and asks me for credentials (NOT the activation screen but the start screen). When I enter them it claims to have no internet connection.

 

designer 2.0.zip publisher 2.0.zip photo 2.0.zip

[Leigh]

On 11/16/2023 at 5:29 PM, PotatoCarl said:

Okay. when I do NOT select to import Version 1, it starts, however, it closes again after a few seconds.

One of the programs (publisher) does not have a connection to the account  and asks me for credentials (NOT the activation screen but the start screen). When I enter them it claims to have no internet connection.

 

designer 2.0.zip 3.14 MB · 0 downloads publisher 2.0.zip 21.74 kB · 0 downloads photo 2.0.zip 240.21 kB · 0 downloads

Is it possible to tell me what you're using to the virtualise Windows?

[PotatoCarl]

KVM/QEMU

[Leigh]

On 11/20/2023 at 12:28 PM, PotatoCarl said:

KVM/QEMU

Thanks!

Would it be possible to send me a copy of your Log.txt from %APPDATA%\Affinity\Photo\2.0\ ?

[PotatoCarl]

here it is:

[2023-11-22T16:23:14.185+0100] Affinity Photo 2
[2023-11-22T16:23:14.186+0100] IsSandboxed: No
[2023-11-22T16:23:14.186+0100] AppDataPathForCurrentUser: C:\Users\crash\AppData\Roaming\Affinity\Photo\2.0
[2023-11-22T16:23:14.186+0100] AppDataPathForCurrentUserPersisted: C:\Users\crash\AppData\Roaming\Affinity\Photo\2.0
[2023-11-22T16:23:14.187+0100] AppDataPathForAllUsers: C:\ProgramData\Affinity\Photo\2.0
[2023-11-22T16:23:14.187+0100] CommonDataPathForCurrentUser: C:\Users\crash\AppData\Roaming\Affinity\Common\2.0
[2023-11-22T16:23:14.187+0100] CommonDataPathForCurrentUserPersisted: C:\Users\crash\AppData\Roaming\Affinity\Common\2.0
[2023-11-22T16:23:14.188+0100] CommonDataPathForCurrentUserPersistedBuildInvariant: C:\Users\crash\AppData\Roaming\Affinity\Common\2.0
[2023-11-22T16:23:14.188+0100] CommonDataPathForAllUsers: C:\ProgramData\Affinity\Common\2.0
[2023-11-22T16:23:14.189+0100] TempPathForCurrentUser: C:\Users\crash\AppData\Roaming\Affinity\Photo\2.0\temp
Begin check for updates...[DXGI] Enumerating adapters
Microsoft Basic Render Driver
    HardwareID: PCI\VEN_1414&DEV_008C&SUBSYS_00000000&REV_00
    LUID: 0x983C
Microsoft Basic Render Driver
    HardwareID: PCI\VEN_1414&DEV_008C&SUBSYS_00000000&REV_00
    LUID: 0x9780
[OpenCL] Found 1 platforms:
Name: Intel(R) OpenCL
    Vendor: Intel(R) Corporation
    Version: OpenCL 1.2
[2023-11-22T16:23:17.122+0100]     Installed
[2023-11-22T16:23:18.043+0100] ...check for updates completed
[2023-11-22T16:23:18.054+0100] No update is available.
[2023-11-22T16:23:26.725+0100] Wintab: Failed to load Wintab32.dll
[2023-11-22T16:23:26.725+0100] Wintab: Failed to create tablet context
[2023-11-22T16:23:26.727+0100] Content migration already offered previously

 

[Leigh]

Thanks for sending the log.txt. Sorry for the delay in replying, it's been really busy with Black Friday 😰

I've not really spoken to any other users using KVM/QEMU but I know the apps work in virtualised environments. The "Please Try Again" message can happen if there's an issue with the app accessing the %APPDATA%\Affinity\Common\2.0 folder or the .dat files inside it. Can you try renaming this folder and try again?

The issues you're having could also be down to how the VM is setup to access the network from within KVM/QEMU. Do you know how it's setup?

[PotatoCarl]

Well, it is a "local" setup, meaning that the folder are not on a network drive.

okay, after removing the files under "common" it seems to work.

The good-ole-turn-off-turn-on-try-again seems to have worked...

Edited November 30, 2023 by PotatoCarl
Other things happened the second time it was tried.

[Leigh]

That's good to hear. I've been sat on a plane where the Captain announced he was turning it off and back on to fix an issue. Didn't Crash, true story

Hoping it continues to work 🤞

[PotatoCarl]

THis happens more often than you think, I had it myself a few times...