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

Question

Question

weblink8 ERR_RESPONSE_HEADERS_MULTIPLE_CONTENT_ DISPOSITION

asked on March 14, 2023

is any solution for this :

weblink8 ERR_RESPONSE_HEADERS_MULTIPLE_CONTENT_ DISPOSITION

0 0

Answer

SELECTED ANSWER
replied on March 14, 2023

Husham,

You can either use Laserfiche Workflow to create an automated process to update each entry or you can use straight SQL on the Laserfiche Database Server to update the file names all at once (This is the fastest and easiest but also the most dangerous).

If you decide on the SQL method, make sure you have a backup of the database just in case something seriously goes wrong.

To remove all commas in the file name, run the following SQL on the Laserfiche Database Server against your Laserfiche Repo Database:

Update dbo.toc set name = REPLACE(name,',','') where etype = -2

Hope this helps!

Wesley Funderberg

1 0

Replies

replied on March 14, 2023

Husham,

 Usually this error occurs when there are special characters in the name of the file such as ' (quotes) or , (commas). Remove or replace these characters with an underscore to see if the error goes away.

 

Hope this helps!

Wesley Funderberg

1 0
replied on March 14, 2023

Thank you Wesley,

It's Fixed, it was a comma

Any way I can automate replacing the comma, I have thousands of documents.

Regards

yes

1 0
SELECTED ANSWER
replied on March 14, 2023

Husham,

You can either use Laserfiche Workflow to create an automated process to update each entry or you can use straight SQL on the Laserfiche Database Server to update the file names all at once (This is the fastest and easiest but also the most dangerous).

If you decide on the SQL method, make sure you have a backup of the database just in case something seriously goes wrong.

To remove all commas in the file name, run the following SQL on the Laserfiche Database Server against your Laserfiche Repo Database:

Update dbo.toc set name = REPLACE(name,',','') where etype = -2

Hope this helps!

Wesley Funderberg

1 0
replied on March 14, 2023

Thank you,

we ended up with the SQL Solution

Again thank you for your help.

 

0 0
replied on March 14, 2023

I don't see a record of a previously-reported bug like that. Can you describe what you did to get this error? I see from a quick searching that it might be related to a download attempt with certain characters in the name?

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

Sign in to reply to this post.