Your error-message may not directly hint to the causing issue else it might be just an aftereffect.
Set up in the same way could mean to have quite different environments in the end ... My preferred way of doing a migration is to start with mirroring the existing environment. Installing the same OS and QlikView release and transferring all data + applications + settings (you need to stop all services to copy everything) from the old to the new environment and preparing the QlikView configurations before you start the services (changing the server-name in all config-files) and changed the prod-licence to the temporary one or just testing with the prod as long as you didn't used them on both environments at the same time.
If everything went well everything is there - licenses, users, tasks and they run and you could access them from the access point. If it looked like unnecessary efforts it puts itself into perspective by any kind of trouble-shooting because if it worked it means that all kind network + authentication + group policies stuff is ok. which isn't an obviousness. If there are instead any issues it's quite unlikely that any of the QlikView configuration is involved and that the cause is anywhere on the outside of Qlik.
