So testing out PVS 2407 on Server Core. Getting failures on the Config Wizard. Looking at the logs I am getting the following errors. ERROR:SqlException caught, Number = 208, Message = Invalid object name 'DatabaseVersion'. [MapiConnection.cs(1539): GetFilledDataSet]

Would you be prepared to share the complete configwizard.log file?

So doing an install from GUI worked fine. So I tried joining that farm from the core and it failed. Here are the logs from each of them.

Well, you used a different database (farm) in those two -- seems that in the failing case, the database existed but was not initialized properly so the DatabaseVersion table doesn't exist. In the working case the database existed and has an existing schema version.

I tried both. Creating a database from Core, that failed. Then I created a database from server with desktop experience, it worked. And then went to server core to try and join that farm and it also failed. The reason you see 2 different names is because I used a different database for each instance.

Dont suppose you have the cw log from that very first attempt to create in core do you? Also - with the 'joinerror' one this is, from what you said, the case where you created the DB from server-with-desktop and then tried to join the same farm from Core? You might also use SSMS to look at the database used in the failing case - I suspect you will find it empty but I could be wrong...

The newinstall was the log from a first attempt to create that database. The database created has some structure, but not everything. I can blow the DB away and do another run if you want.

Wait... confused now... I assumed newinstall was a working case... let me look more closely at it...

Both were failure logs. It's odd because I used the same account on the desktop experience machine and it worked fine. So something with how core isolates things from desktop experience seems to be the main issue. WEM and DDC both installed and worked fine on their core instances.

OK... so - you have a bunch of databases in that SQL server instance which is what was confusing me -- because there is code in the CW that enuymerates all databases to check which ones are PVS databases (which is does by looking for the DatabaseVersion table) -- obv the non-PVS ones wont have that so you see an error for those - confusing I know! (certianly confused me 🙂 ) Now I'm past that... I see

newinstall

creates the db properly including adding sprocs and triggers, creates the farm, site ans server records - in fact gets all the way through and then at the very end declares a failure... because somewhere along the way something bad happened.

Yeah, and I see authentication errors in both the logs, and in SQL with the same account that works on the gui desktop versions. So I wonder if Core has some form of impersonation lockdown, or elevation capability that the configwizard uses for config.

OK - there is one hint in the answer file that could be relevant -- it seems that in the newinstall log, you are creating a db

PVSCRNew

BUT there was left over configuration in the registry from a previous use of PVS that pointed to a database

pvs-sr

- immediately after we detect that, there is ONE report of a failure to connect to the new database using integrated windows auth, even though we've been doing this all along... currently reviewing this with the team...

Ok. I can redeploy this machine pretty easily, so if you want me to do a fresh computer with first time run let me know.

I think we need to debug this here -- since we support installing on Server Core now we had better make sure it works in all cases! Let me get back to you once we have a better idea...

Server Core 2025, and yes I was logged in with the domain admin account.

Thanks. You know, we don't officially support S2025 yet 🙂 (testing so far has been good but I dont think we've tried the new server core).

Yeah, I cam do up a 2022 core, or an azure stack core if you want as well. I always push the envelope when it comes to the os. 😉

Let us continue to look into it first... will get back to you...

So I tested with 2022 core, and it worked. I am going to continue testing.

We did wonder if it might be the join to a CVAD site that was causing this so thanks for validating that... seems that there are multiple issues though...

Sure, I will run through this later today and get you some logs.

• When you say "CVAD tie-in" are you talking about the option in the config wizard to register with an on-prem DDC? So that you can use studio provisioning of PVS VDAs? The only way to do this is via the config wizard. • Not sure what you meant by "installed PVS without VDA" -- are you saying you install the VDA on the PVS server machine? Not syaing it wont work but I am sure we dont test that... • Any chance you could share your answer file? (suitably redacted of course)...

Yes, when I say VDA I mean the CVAD tie-in for studio on-prem. And yes, I removed the computer account. It was the same machine, but just the process of putting it in during the configwizard I believe is required. And when it was there it had problem switching to it.

Can you explain what you mean by "CVAD tie-in for studio on-prem" -- are you referring to the page in the config wizard where you can register the PVS server with your on-prem DDC? There's nothing to be installed for that, just configuration. Apologies if question is obvious but we dont use the same terminology so I want to be sure we are on the same page. If you remove the SQL login for the computer account then yes, the config wizard does create that if it doesn't exist -- and this also has to be correct in order for you to be able to run the PVS servers under the network account.

image.png

Yup that's the one I was thinking. Thanks...

I don't use an answer file, I just run through the install directly. Pretty generic of a setup.

Ah sorry - I assumed you were using an answer file on server core.. so far we've not been able to reproduce your problem but we'll keep on looking...

So I do generate an SSL certificate for the machine remotely, as you need to select one in order to use the Join your farm with your Citrix Virtual Apps and Desktops site. I use the same Webserver certificate template from my AD Certificate Server, so it will be trusted by domain objects. Could there be something with that certificate?

I dont think so... but thanks for the update.