Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Syed Kausar Husain (SYEDKAUSARHUSAIN)
Capgemini, Sweden
CLSA
Capgemini, Sweden
SE
SYEDKAUSARHUSAIN Member since 2010 14 posts
Capgemini, Sweden
Posted: Mar 6, 2017
Last activity: Mar 21, 2017
Posted: 6 Mar 2017 21:49 EST
Last activity: 21 Mar 2017 7:00 EDT
Closed
Solved

Cannot edit data table in excel in version 6.3 SP1

Hi All,

We have upgraded application from 5.5 to 6.3 SP1.

Now in 6.3 SP1, not able to edit data table in excel. On click of button 'edit in excel' excel opens without any data with below error message in popup.

"Failed to re-attach server session. -2147012867, A connection with the server could not be established."

Same thing works in 5.5 on same machine. Its kind of one top priority issue currently, please anyone help to fix it .

Thanks in advance.

Regards,

Kausar

***Updated by Moderator: Marissa to add SR details to main post***

To see attachments, please log in.
Data Integration
Security
Support Case Created

Accepted Solution

Posted: 7 years ago
Posted: 7 Mar 2017 22:47 EST
Sudhish Othoyoth Puthiyapurayil (othos) Senior Technical Solutions Engineer
Pegasystems Inc.
IN

Hi Kausar,

The reason for rejection of the ticket reopen is valid.Please have a look into the below policy.

It is Pegasystems’ policy not to backwards-test new versions of Platform Components with older releases of PRPC. Support for new platform products is provided through newer versions of PRPC software.  If you choose to upgrade Platform Components to the latest releases, but want to stay on older releases of PRPC, you may enter support requests for any problems encountered. However, if the root cause of these problems stems from the fact that the older versions of PRPC were not designed to handle functionality in the newer Components, Pegasystems may request that you upgrade your PRPC version to a release that directly supports that newer Component, as listed in this Guide.

Please share me the requested tracer by testing this use case in SSO environment and will try to assist you.

Note:  It is always advisable to use the supported versions by referring to the platform support guides of PRPC. So you will get assistance from PEGA since it was tested/certified by PEGA.

User is using the following unsupported versions
1. MS Excel version 14.0.7173.5000 (32-bit)
2. IE 11You have to use compatible versions as suggested in the below support guide.

Show More

Hi Kausar,

The reason for rejection of the ticket reopen is valid.Please have a look into the below policy.

It is Pegasystems’ policy not to backwards-test new versions of Platform Components with older releases of PRPC. Support for new platform products is provided through newer versions of PRPC software.  If you choose to upgrade Platform Components to the latest releases, but want to stay on older releases of PRPC, you may enter support requests for any problems encountered. However, if the root cause of these problems stems from the fact that the older versions of PRPC were not designed to handle functionality in the newer Components, Pegasystems may request that you upgrade your PRPC version to a release that directly supports that newer Component, as listed in this Guide.

Please share me the requested tracer by testing this use case in SSO environment and will try to assist you.

Note:  It is always advisable to use the supported versions by referring to the platform support guides of PRPC. So you will get assistance from PEGA since it was tested/certified by PEGA.

User is using the following unsupported versions
1. MS Excel version 14.0.7173.5000 (32-bit)
2. IE 11You have to use compatible versions as suggested in the below support guide.

Please find the below PDN document links referring to the same.
https://docs-previous.pega.com/platform-support-guide-prpc-5x-and-6x
https://docs-previous.pega.com/support-internet-explorer-11


Show Less
To see attachments, please log in.
Posted: 7 years ago
Posted: 7 Mar 2017 3:17 EST
Syed Kausar Husain (SYEDKAUSARHUSAIN)
Capgemini, Sweden
CLSA
Capgemini, Sweden
SE

Hi Othos,

Currently we are not in SSO and testing it without SSO. Maybe same will come up in SSO too.

Might be I cannot share fddler and WinHttptrace due to security issue of project. I will check about it and will let you know.

We already raised a SR for this but did not get any soluiton from PEGA. Will be a great help if anyone can help ot fix it.

Thanks,

Kausar

 

 

 

 

To see attachments, please log in.
Posted: 7 years ago
Posted: 7 Mar 2017 3:32 EST
Sudhish Othoyoth Puthiyapurayil (othos) Senior Technical Solutions Engineer
Pegasystems Inc.
IN

Hi Kausar,

What you mean by "did not get any solution from PEGA" ? Whether SR is still in open status and pending for technical assistance ? .Also, can you please share the SR No?

I can understand the security concern you have mentioned, but we can't start the analysis without necessary logs. Debugging at the site will be only applicable with SR .

 

To see attachments, please log in.
Posted: 7 years ago
Posted: 7 Mar 2017 3:55 EST
John Pritchard-Williams (JOHNPW_GCS) Client Support Team Lead
Pegasystems Inc.
GB

Agreed: we really need to start by looking at a HTTP trace here.

One very common cause of the 'edit in excel' mechanism failing - which we need to eliminate (using HTTP logs) or confirm: is if there is a Load Balancer or other type of Proxy in-between the Browser and the Application Server.

The 'Edit in Excel' mechanism relies on being able to 'hand-over' an existing HTTP session from a Browser to Excel - using an 'ActiveX' to pass the required information for the HTTP Session in an XML file.

If (for instance) a Load-Balancer is not set up to provide 'sticky sessions' based on the 'PegaRULES' (for the prpc session state) and the 'JSESSION' (for the Application/Browser session state) correctly: this can lead to this type of issue.

One of the tricky and possibly unexpected things here; is that because Excel 'takes over' from the Browser; the 'user-agent' HTTP Header changed (but the PegaRULES and JSESSION cookies do not) - if rules in a Load Balancer don't expect this user-agent change, they might not allow the required HTTP Routing to occur here.

A HTTP Trace is absolutely required here to make progress.

 

To see attachments, please log in.
Posted: 7 years ago
Posted: 7 Mar 2017 13:09 EST
Syed Kausar Husain (SYEDKAUSARHUSAIN)
Capgemini, Sweden
CLSA
Capgemini, Sweden
SE

Hi Othos, appreciate very much for your quick responses.

I fixed it in non-SSO Dev environment using F12Developer tools after using couple of hit and trials. But if you know any other solution then I would like to know it.

SR-B12543 status is 'Resolved-Reopen Rejected'. Pega rejected this SR saying we are using unsupported versions MS Excel and IE and there is no support for incompatible versions even though same works in 5.5.

Thanks,

Kausar 

 

To see attachments, please log in.

Accepted Solution

Posted: 7 years ago
Posted: 7 Mar 2017 22:47 EST
Sudhish Othoyoth Puthiyapurayil (othos) Senior Technical Solutions Engineer
Pegasystems Inc.
IN

Hi Kausar,

The reason for rejection of the ticket reopen is valid.Please have a look into the below policy.

It is Pegasystems’ policy not to backwards-test new versions of Platform Components with older releases of PRPC. Support for new platform products is provided through newer versions of PRPC software.  If you choose to upgrade Platform Components to the latest releases, but want to stay on older releases of PRPC, you may enter support requests for any problems encountered. However, if the root cause of these problems stems from the fact that the older versions of PRPC were not designed to handle functionality in the newer Components, Pegasystems may request that you upgrade your PRPC version to a release that directly supports that newer Component, as listed in this Guide.

Please share me the requested tracer by testing this use case in SSO environment and will try to assist you.

Note:  It is always advisable to use the supported versions by referring to the platform support guides of PRPC. So you will get assistance from PEGA since it was tested/certified by PEGA.

User is using the following unsupported versions
1. MS Excel version 14.0.7173.5000 (32-bit)
2. IE 11You have to use compatible versions as suggested in the below support guide.

Show More

Hi Kausar,

The reason for rejection of the ticket reopen is valid.Please have a look into the below policy.

It is Pegasystems’ policy not to backwards-test new versions of Platform Components with older releases of PRPC. Support for new platform products is provided through newer versions of PRPC software.  If you choose to upgrade Platform Components to the latest releases, but want to stay on older releases of PRPC, you may enter support requests for any problems encountered. However, if the root cause of these problems stems from the fact that the older versions of PRPC were not designed to handle functionality in the newer Components, Pegasystems may request that you upgrade your PRPC version to a release that directly supports that newer Component, as listed in this Guide.

Please share me the requested tracer by testing this use case in SSO environment and will try to assist you.

Note:  It is always advisable to use the supported versions by referring to the platform support guides of PRPC. So you will get assistance from PEGA since it was tested/certified by PEGA.

User is using the following unsupported versions
1. MS Excel version 14.0.7173.5000 (32-bit)
2. IE 11You have to use compatible versions as suggested in the below support guide.

Please find the below PDN document links referring to the same.
https://docs-previous.pega.com/platform-support-guide-prpc-5x-and-6x
https://docs-previous.pega.com/support-internet-explorer-11


Show Less
To see attachments, please log in.
Posted: 7 years ago
Posted: 7 Mar 2017 13:12 EST
Syed Kausar Husain (SYEDKAUSARHUSAIN)
Capgemini, Sweden
CLSA
Capgemini, Sweden
SE

Hi Marissa,

SR # is B12543. I have resolved this issue in DEV environment (without SSO) using F12 developer tool.

But I would like to hear a better solution from Pega that will work with SSO as well.

Thanks,

Kausar 

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice