Home > App-V > App-V 4.5: The App-V Management Server Service fails to start with Service-Specific Error 268480320

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.”

Categories: App-V Tags: , , , , , , ,
  1. canyouflybobby
    November 30, 2011 at 5:53 pm

    For some reason we moved our APP-V service to a SQL cluster. We get this error now when we try to enable the SQL logging which was configured to the old SQL server. Changing to the new sql cluster name either with dynamic port or 1433. The APP-V service won’t start ??
    APP-V is working normally but not the logging feature.

  2. December 6, 2011 at 4:29 pm

    So from what I am understanding, you have actually moved the App-V database? Are you getting this error?

    Take a look at this: http://blogs.technet.com/b/appv/archive/2011/10/26/error-268480357-starting-an-app-v-management-server-with-dynamic-sql-ports.aspx

  3. January 11, 2012 at 2:28 pm

    I am receiving this error and tried your resolution above, however the service still will not start, giving the same error. When I change to use dynamic ports, I get the Error 268480357, when I change to static ports, I get the Error 268480320. Would you have any suggestions?

  4. May 8, 2014 at 2:00 am

    A person essentially lend a hand to make severely posts I might state. That is the very first time I frequented your website page and to this point? I surprised with the research you made to create this particular put up incredible. Excellent job!

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: