Hi,
So nothing like being on the cutting edge......
I have been testing Server 2019 RDS and so-far-so-good apart from an issue with the Windows Search Service.
It appears that in Server 2019 each user gets their own search database EDB file in their profile path (appdata\roaming). e.g.
C:\Users\username\AppData\Roaming\Microsoft\Search\Data\Applications\S-1-5-21-3901271148-1553943383-1671037523-1629\S-1-5-21-3901271148-1553943383-1671037523-1629.edb
When they log on and log off; this is connected to the search service and the following event log is generated
Source:ESENT
EventID: 326
SearchIndexer (10896,D,50) S-1-5-21-3901271148-1553943383-1671037523-1629: The database engine attached a database (3, C:\Users\username\AppData\Roaming\Microsoft\Search\Data\Applications\S-1-5-21-3901271148-1553943383-1671037523-1629\S-1-5-21-3901271148-1553943383-1671037523-1629.edb).
(Time=0 seconds)
Unfortunately it appears that this process is not very stable and on some logons the database in the users profile does not attach and the following error is generated
Source:Search
EventID: 3057
The plug-in manager <Search.TripoliIndexer> cannot be initialized.
Context: S-1-5-21-3901271148-1553943383-1671037523-1629 Application
Source:Search
EventID: 3028
The gatherer object cannot be initialized.
Context: S-1-5-21-3901271148-1553943383-1671037523-1629 Application, SystemIndex Catalog
Details: The specified object cannot be found. Specify the name of an existing object. (HRESULT : 0x80040d06) (0x80040d06)
And a few more similar but related errors....
No subsequent logon/off will succeed in attaching the database until the Windows Search service is restarted
I am not testing with User Profile Disks or Roaming Profiles
There is no AV on the server
Any ideas?
Andy
Andrew