Qlik Community

QlikView Publisher

Discussion Board for collaboration on QlikView Publisher.


Breathe easy -- you now have more time to plan your next steps with Qlik!
QlikView 11.2 Extended Support is now valid through December 31, 2020. Click here for more information.

Not applicable

Migrating tasks to a new server

Hello Hello,

I can find alot of good information about migrating on the same server. The thing is that none of the tips are working in my environment.

The old servers are both Server 2008 R2 with QV 10

On the app-srv-qv1 the client installed Qlikview server and Qlikview webserver.

On the app-srv-qv2 the client installed Qlikview directory services, management services and distribution services (publisher).

The new servers are both Server 2012 with QV 11.2 SR6 and are in the same domain as the old ones.

They are called appsrv-qv1p and appsrv-qvp2p. This cannot be changed.

The same roles are installed like on the old ones.

The folder structure is identical on the old and new servers.

We have copied the old QVPR folder to the new server, just like most manuals say (including the ini file and such). We then renamed everything in QMC en voila everything is up and running. Except one thing.... the tasks.

We see the tasks and we see the source documents. The thing is that the tasks are merged with the source documents in the <orphans>  folder within QMC.

So you have a list of tasks, a list of source documents (without tasks) and a list of the same source documents in the orphans folder (which have tasks).

Does anyone have a suggestion how to fix this? What did we do wrong? There are 100+ tasks

Tnx in advance!

4 Replies

Re: Migrating tasks to a new server


The below post might help you.




Not applicable

Re: Migrating tasks to a new server

Moving the QVPR database from its default location where the QMS (version 11) is located, and place it on a Windows share on a network. To move the QVPR, the whole application data folder for QMS needs to be re-located.


  1. Stop the QlikView Management Service via the Windows Services console.
  2. Locate the QMS application data folder on the server that hosts the QMS service. Default location are either of the following:
    • Windows Server 2008/Windows 7: C:\ProgramData\QlikTech\ManagementService
    • Windows Server 2003/Vista/XP: C:\Documents and Settings\All Users\Application Data\QlikTech\ManagementService
  3. Create the new folder or share for the QMS application data, for example \\server.domain.local\my-share\ManagementService. Note: Make sure that the service account running the QMS service has the appropriate Read/Write permissions on this folder or share. If the service account for some reason does not have these permissions, unexpected behavior in your QlikView environment might occur.
  4. Move or copy all the contents of the old folder to the new one.
  5. Locate the configuration file for QMS in the Program Files folder, C:\Program Files\QlikView\Management Service\QVManagementService.exe.config, and open it in Windows Notepad or any other text editing tool.
  6. In the setting "ApplicationDataFolder", set the "Value" attribute to the new folder path. The settings node will then look something like this:

<add key="ApplicationDataFolder" value="\\server.domain.local\my-share\ManagementService"/>

  1. Save and close the .config file.
  2. To be sure that the change applies, rename the old folder C:\ProgramData\QlikTech\ManagementService to something else, for example C:\ProgramData\QlikTech\moved-ManagementService.
  3. Start the QlikView Management Service via the Windows Services console.

Note: This will move the QMS logs, the Publisher LEF file and all other settings that belong to QMS as well.

Not applicable

Re: Migrating tasks to a new server

Already tried this one. Normally it works, but with this case it doesn't. Tnx for the input!

Not applicable

Re: Migrating tasks to a new server

Whats the difference between this post and the post from Ashfaq?

Because in both we copy/move the "old" QVPR to the new server...

In the meantime we found out that we can copy the sourcedocument/task from the <Orphans> section to the good section. This works, but is a bit more work.