You are viewing limited content. For full access, please sign in.

Question

Question

WebLink "error the operation completed successfully"

asked on September 9, 2022

I have a number of users that are reporting issues when viewing pdf documents in WebLink.    The documents do not display and the thumbnail image(s) has the message "Error The operation completed successfully".  See attachment.

This issue is not consistent,   occasionally reopening the document it will open correctly.   Occurs in Edge and Chrome.   There is never an issue viewing documents when downloaded or using the desktop client.

I am not sure what services/processes to look at for issues.  I don't see anything in my event logs.   If anyone can give me a direction of what to investigate to correct this problem!

WebLink: 11.0.2111.777

WebLink_Err1.PNG
WebLink_Err1.PNG (28.89 KB)
1 0

Replies

replied on December 20, 2022

Hi Andrews,

 

I just had a similar issue on our weblink. I fixed it by restarting the application pool that is connected weblink instance..

1. Open IIS

2. Applications Pools

3. Default application name should be "WeblinkAppPool"

 

IF you still are having issues try the item below.

 

Remove ASP.NET Temp Files in Windows

To clear the temporary files do the following on both the Web Server:

  1. Log in to the server and open IIS.
  2. Stop IIS service. Run “iisreset /stop” in the command prompt to stop the IIS service.
  3. Navigate to the below directories:
    • “C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\”
    • “C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\”
  4. Remove all files under both directoires.
2 0
replied on December 29, 2022

We had the same issue come up, and this fix worked for us. Thanks for posting.

1 0
replied on February 21

Restarting the WeblinkAppPool resolved this issue for us.

Thank you!

Christine

0 0
replied on February 21

We fixed a cause of this in December 2021. So if you are on an old release, you should upgrade and it might be addressed. We have seen reports of people running into this even with that fix, but we haven't been able to reproduce it internally. If it happens to you regularly, consider opening a support case and we can take a look.

1 0
You are not allowed to follow up in this post.

Sign in to reply to this post.