Posts Tagged ‘aadconnect’

I was recently trying to Upgrade the AADconnect server to stop the high 100% CPU issues

After running the MSI . then running AzureADConnect.exe , the upgrade came up with the error

Unable to upgrade the LocalDB Sql Express database Running

I went to the event log and found the error :

Error installing msi package ‘SqlLocalDB.msi’. Full log is available at ‘C:\ProgramData\AADConnect\SqlLocalDB_Upgrade-20180813-094321.log’.

I checked through the Log and there seemed to be lots of 1603 errors

I ran the SQL Setup ( C:\Program Files\Microsoft Azure Active Directory Connect\SetupFiles\SqlLocalDB.msi ) manually and it asked if I wanted to upgrade my LocalDB from 2008 to 2012 which I said yes to 


The installer then came up with the error SQL Server 2012 Express LocalDB

Could not open key: UNKNOWN\Components\. Verify that you have sufficient access to that key, or contact your support personnel.

I ran through the workaround 1 from this guide

https://blogs.msdn.microsoft.com/sqlserverfaq/2010/03/30/sql-server-2008-setup-fails-to-install-with-error-1402/

And then the SqlLocalDB.msi finished successfully , I was then able to run through the AzureADConnect.exe upgrade

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

A Server 2012 R2 started getting VSS Writer Errors randomly in Veeam backup job. The server is running AADconnect which is set to autoupdate

A restart of the VSS SQL Writer which usually fixes this did not resolve the issue.

A look in the event log shows

A VSS writer has rejected an event with error 0x800423f4, The writer experienced a non-transient error. If the backup process is retried,
the error is likely to reoccur.
. Changes that the writer made to the writer components while handling the event will not be available to the requester. Check the event log for related events from the application hosting the VSS writer.

Operation:
PrepareForSnapshot Event

Context:
Execution Context: Writer
Writer Class Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
Writer Name: SqlServerWriter
Writer Instance Name: SQL Server Code-Named ‘Denali’ CTP2:SQLWriter
Writer Instance ID: {6c73bfe9-f82f-4854-bec4-4382c314a583}
Command Line: “C:\Program Files\Microsoft SQL Server\90\Shared\sqlwriter.exe”
Process ID: 4292

With some

SQLVDI: Loc=SignalAbort. Desc=Client initiates abort. ErrorCode=(0). Process=4292. Thread=3940. Client. Instance=LOCALDB#SHDA41B2. VD=Global\{9C831400-DE4D-4364-BA22-A8299CF545FC}4_SQLVDIMemoryName_0.

Looks like you need to download the SQL Fix from here : https://support.microsoft.com/en-us/help/2983175/cumulative-update-package-2-for-sql-server-2012-sp2

Mirror Here : https://mega.nz/#!3AZ3gK7I!kDPhnAlur4XtslKxGXwmbnLitJiwN9R6rK-z4Rh0N-s

 

**Update , fix does not seem to work

A repair on the SQL database and then run the below script

Looks like this might be an issue with AADcoonect

https://github.com/pariswells/pariswells.com/blob/master/fixaadconnectvsswriter.ps1

 

**Update

 ADSync launches an SQL Server Local DB under it’s own user account
– The User Profile Service thinks ADSync is no longer logged on, and unloads the registry
– SQL Server though still has handles to the registry, but they’re invalid now

Detailed explanation:
https://support.microsoft.com/en-us/help/2287297/a-com-application-may-stop-working-on-windows-server-2008-when-a-user

In short: Computer Configuration->Administrative Templates->System->User Profiles->Do not forcefully unload the user registry at user logoff

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)