App-V 4.5: The App-V Management Server Service fails to start with Service-Specific Error 268480320
You may get the following error message when you try to start the App-V Management Server service:
“Windows could not start the Application Virtualization Management Server on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code 268480320
System Event Log will show the same error under Event ID 7024.
You will also see the following error in the SFT-SERVER.LOG file on the App-V Management server:
SW_ProtocolServer::ConfigureLogPipeline – – – – 1 44864 “Unexpected Error creating Log Pipeline.
This relates to the Provider Pipeline Logging Configuration which is configured at the Server Group Level.
You may also see a false positive log message stating that the server was unable to connect to the data source. The server is able to connect, but the database records it is reading in for the pipeline (to the MESSAGE_LOG table) is incorrect.
To resolve and prevent this issue, it will require correct log pipeline configuration. This is done as follows:
1.) Launch the Application Virtualization Management Console.
2.) From the Server Groups node, right-click the Server Group your App-V Server belongs to and select “Properties.”
3.) Click on the “Logging” tab.
4.) Select “SQL Database” and select “Edit.”
5.) Make necessary modifications under these considerations:
– If the SQL Server you are connecting to contains multiple instances, you will need to select “Dynamically Determine Port.”
– If the SQL Server you are connecting to resides on the default instance, select port 1433 and disable “Dynamically Determine Port.”
– If the SQL Server you are connecting to is using a non-standard port, specify the port and disable “Dynamically Determine Port.”