EPM report does not connect to model after login PCM

[Olj]

Hi,

We use EPM add-in for Excel for PCM reporting.

We have some PCM report created via EPM add-in (local connection). On author PC - report works OK.

But when we move and running this report on another PC we have some issue:  

1.In Excel user create local PCM connection

2. Then login to model via EPM

3. Open prepared report

4. Data does not refreshed

We found cause :

Report doesn't really connected to Model:

As workaround User must to do:

But this workaround is not unaccesstable for our customer.

How can we solve that issue?

Thanks in advance...

[Former Member · Accepted solution]

Hi Daulet

Ok firstly lets eliminate the obvious. The EPM10 reports can store connections and the previous connection may not be viable for you client for all sorts of reasons, domain compatibility, ports, wireless connectivity etc etc.

So just do this. Report Actions => Manage Connections => select the required connection (check if you have multiple connections) => Report connections => Select the required connection.

If the problems persists you either have domain issues where different client machine have problems establishing comms on the same EPM 10 connection. Possible though unlikely.

What is more likely is that the EPM10 client install was not compatible with the EPM10 client that created that connection. If all other issues such as stored connections and domain to client machine issues are ruled out it is the only possible cause.

I suggest you check and aim for EPM10 client compatibility across all your client installs, create a new connection for the report and store this connection.

Let us know how you get on.

[Olj · Accepted solution]

Hi Michael, problem with report connection to model solved,

but all remote users login too long (about 30 mins) via EPM, what can be wrong?

[Former Member · Accepted solution]

The remote connection does add an overhead of several seconds for a typical connection to a report with zero load (no query results being returned)

If you have a connection to several report in the same worksheet then you can multiply your delay per report by the number of reports, plus any load (query results).

If each of the reports has several connections each of which is also being returned then the delay can also be added to the delays mentioned above.

In short you can end up with very large delays especially using remote connection on reports with multiple connections and worksheets with several reports.

It might be worth creating a blank report (closed circuit test) with a direct connection and test the time, do the same with the remote connection.

Then get the report you had the problems with and time taken to make a direct connection and do the same test with remote users.

The benchmark times should tell you the following:

1) If the direct connection users get both reports with little or no delay, there is problem with your remote connection terminal server (firewall, certificates, network delays)

2) If both direct and remote users get the blank report quickly then you have issues with that report and you need to simplify the number of connection stored or reports embedded in the worksheet

3)If the direct connections users get delayed on both reports but no as much as the remote connection users. Then it is your network (WAN and perhaps LAN too) that maybe the issue.

Hope this helps.

[april_shultz]

Hello,

If this works on one machine and not another then the problem is client specific and you will need to determine the differences in between the 2 machines.

What version SP of the EPM addin is installed on the non working machine and what SP on the working machine?

What version of Office is on the non working machine and what version of Office is on the working machine?

Have you looked at the non working machine application and system event logs? Is there anything in them?

Thanks

April

[Olj]

Hi April,

We tried on terminal server, client PC - the same result!

Also we tried EPM SP16, 18, 20, 22, 25,   .NET 3.5 and 4.0 version.

Looks like report cannot connect to new connection (same model)