Hello!

In a PAW dashboard, I have a public websheet on a tab. This websheet renders as expected under my profile (Admin - Full Control) without any issue. However, this is not the case for other users. Specifically, another Admin/Full Control user and an Analyst/View Only user click on the tab with the worksheet and get the below message which states that Logging on to the server failed. Note that all other tabs without the Excel files are working as intended - so the connection to the server is alive and well.

The message is not consistent, as the users can sometime render the websheet, but it mainly produces the error. So far, we have not found any consistencies to help (clearing cache, changing browsers, resetting/resaving book in PAW or PA). I can use Native authentication on my computer, login as either one of these users, and recreate the message. The other admin user can use native authentication under my account and see the report working as expected on their computer without getting the error. All PAW security (user and workbook that we know of) has been verified and the Excel file is public in the Application folders.

We've also attempted to upload the Excel report from other admin accounts to rule out any concern there with no behavior changes. Has anyone else had this issue and can share resolution? Appreciate any configuration ideas as well to help.

Currently using PAW 90; Local PA 2.0.918.3

Sunny,

You mention "native authentication"; are you using IntegratedSecurityMode=2 such that the users are using integrated login while you can test with native authentication?  There was an old issue that Integrated login would not work for PAW and Websheets for IntegratedSecurityMode=2/3, but I also recall it kind of working a little, and it really just stopped using SSO and autofill in my browser filled the gaps. Anyway, this might be the issue. This was documented years ago, but there is always a chance that it is no longer an issue. Just food for thought.

Configure security mode 2 or 3 to use websheets in Planning Analytics Workspace

Hello!

In a PAW dashboard, I have a public websheet on a tab. This websheet renders as expected under my profile (Admin - Full Control) without any issue. However, this is not the case for other users. Specifically, another Admin/Full Control user and an Analyst/View Only user click on the tab with the worksheet and get the below message which states that Logging on to the server failed. Note that all other tabs without the Excel files are working as intended - so the connection to the server is alive and well.

The message is not consistent, as the users can sometime render the websheet, but it mainly produces the error. So far, we have not found any consistencies to help (clearing cache, changing browsers, resetting/resaving book in PAW or PA). I can use Native authentication on my computer, login as either one of these users, and recreate the message. The other admin user can use native authentication under my account and see the report working as expected on their computer without getting the error. All PAW security (user and workbook that we know of) has been verified and the Excel file is public in the Application folders.

We've also attempted to upload the Excel report from other admin accounts to rule out any concern there with no behavior changes. Has anyone else had this issue and can share resolution? Appreciate any configuration ideas as well to help.

Currently using PAW 90; Local PA 2.0.918.3

Hello!

In a PAW dashboard, I have a public websheet on a tab. This websheet renders as expected under my profile (Admin - Full Control) without any issue. However, this is not the case for other users. Specifically, another Admin/Full Control user and an Analyst/View Only user click on the tab with the worksheet and get the below message which states that Logging on to the server failed. Note that all other tabs without the Excel files are working as intended - so the connection to the server is alive and well.

The message is not consistent, as the users can sometime render the websheet, but it mainly produces the error. So far, we have not found any consistencies to help (clearing cache, changing browsers, resetting/resaving book in PAW or PA). I can use Native authentication on my computer, login as either one of these users, and recreate the message. The other admin user can use native authentication under my account and see the report working as expected on their computer without getting the error. All PAW security (user and workbook that we know of) has been verified and the Excel file is public in the Application folders.

We've also attempted to upload the Excel report from other admin accounts to rule out any concern there with no behavior changes. Has anyone else had this issue and can share resolution? Appreciate any configuration ideas as well to help.

Currently using PAW 90; Local PA 2.0.918.3

scrub the workbook contents for any erroneous server name references in formulas. it's likely that there is something [at least in the publish time state of the book] that is causing it to attempt a multi-server authorization. based on your description it would seem the actual content is content to run on the primary [or successful] systems.

otherwise, can take care to publish the book such that it doesn't have any stale database names in it.

Hello!

In a PAW dashboard, I have a public websheet on a tab. This websheet renders as expected under my profile (Admin - Full Control) without any issue. However, this is not the case for other users. Specifically, another Admin/Full Control user and an Analyst/View Only user click on the tab with the worksheet and get the below message which states that Logging on to the server failed. Note that all other tabs without the Excel files are working as intended - so the connection to the server is alive and well.

The message is not consistent, as the users can sometime render the websheet, but it mainly produces the error. So far, we have not found any consistencies to help (clearing cache, changing browsers, resetting/resaving book in PAW or PA). I can use Native authentication on my computer, login as either one of these users, and recreate the message. The other admin user can use native authentication under my account and see the report working as expected on their computer without getting the error. All PAW security (user and workbook that we know of) has been verified and the Excel file is public in the Application folders.

We've also attempted to upload the Excel report from other admin accounts to rule out any concern there with no behavior changes. Has anyone else had this issue and can share resolution? Appreciate any configuration ideas as well to help.

Currently using PAW 90; Local PA 2.0.918.3

Hello!

In a PAW dashboard, I have a public websheet on a tab. This websheet renders as expected under my profile (Admin - Full Control) without any issue. However, this is not the case for other users. Specifically, another Admin/Full Control user and an Analyst/View Only user click on the tab with the worksheet and get the below message which states that Logging on to the server failed. Note that all other tabs without the Excel files are working as intended - so the connection to the server is alive and well.

The message is not consistent, as the users can sometime render the websheet, but it mainly produces the error. So far, we have not found any consistencies to help (clearing cache, changing browsers, resetting/resaving book in PAW or PA). I can use Native authentication on my computer, login as either one of these users, and recreate the message. The other admin user can use native authentication under my account and see the report working as expected on their computer without getting the error. All PAW security (user and workbook that we know of) has been verified and the Excel file is public in the Application folders.

We've also attempted to upload the Excel report from other admin accounts to rule out any concern there with no behavior changes. Has anyone else had this issue and can share resolution? Appreciate any configuration ideas as well to help.

Currently using PAW 90; Local PA 2.0.918.3