Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Tuesday, March 31, 2015 2:15 PM
Hello everyone,
On a SPWeb, I have a Pages library. Since last week, when I try to save a page, I have this error message : "The URL is invalid, it may refer to a nonexistent file or folder or refer to a valid file that is not in the current Web."
I search into the SharePoint log and I found this line :
System.Data.SqlClient.SqlException: Parameter '@nvarchar8' was supplied multiple times.
Then I launch SQL Server Profiler to find the failing procedure and I found it. The procedure proc_UpdateListItem had @nvarchar8 parameter set twice.
How can I fix this ?
Thank you
Damien
All replies (9)
Tuesday, April 7, 2015 10:15 AM ✅Answered
Hi,
From the error message you provided “System.Data.SqlClient.SqlException: Parameter '@nvarchar8' was supplied multiple times.”, it is related to duplicate ColName for fields on the list. This means there are multiple fields in the list pointing to the same underlying DB column in the database. In the list XML schema, the ColName attribute should NOT be specified in the schema. We should let SharePoint decides which DB column to use.
This article below has the same issue as the customer, please check:
Also as the database is 99% full, and it autogrows with unrestricted growth. If the transaction log of this database is large, please follow the steps below to shrink the log file:
- Take a full backup of the database and transaction log backup.
- Shrink the transaction log to a small size.
Best Regards,
Lisa Chen
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected].
Tuesday, March 31, 2015 4:08 PM
Did you check for any special characters in page name OR URL? or may be total URL length is more than 255 characters.
Tuesday, March 31, 2015 4:11 PM
Hello YashGoley,
The URL is correct (< 255 characters and no special characters). The @nvarchar8 parameter field seems to be the page title (in SQL Server Profiler).
Damien
Wednesday, April 1, 2015 7:23 AM
Hi,
From the error message, This issue may occurs when the Version column is configured as an Indexed Column.
To work around this issue, remove the Version column from the list of Indexed Columns for the list that has this issue. To do this, follow these steps:
- Browse to the pages library.
- In the ribbon, click the Library tab, and then click Library Settings.
- In the fields list, click Indexed Columns.
- In the Indexed Columns list, click Version.
- Click Delete, and then click OK.
- Save the page that you previously experienced the issue with.
Besides, here are similar issues, you can use as a reference:
Best Regards,
Lisa Chen
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected].
Wednesday, April 1, 2015 7:50 AM
Hi Lisa,
There are no indexed column for the library.
But, I think the bug appeared since I active versionning and content approval on the library.
King regards,
Damien CELLE
Wednesday, April 1, 2015 8:05 AM
Hi,
Do you have any Calculated Columns with Formulas?
If yes, can you remove them and try to create a page, to figure out if they are causing the issue.
Ram Prasad Meenavalli | MCITP | MCTS SharePoint | MCPD SharePoint | http://www.spdeveloper.co.in
Wednesday, April 1, 2015 8:06 AM
Hi,
No, there is no calculated columns for this library.
Kind regards,
Damien CELLE
Thursday, April 2, 2015 6:02 AM
Hi,
From the same issue post, You may also need to check the SharePoint Database Server's storage.
Icrease storage size
Reset IIS and Recycle Application Pool of SharePoint site.
Best Regards,
Lisa Chen
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected].
Thursday, April 2, 2015 7:53 AM
Hi,
I check SharePoint Database storage.
Database is 99 % full but it autogrows with unrestricted growth.
Then, the error only occurs on a specific subsite. Other lists on the same database aren't impacted.
Kind regards,
Damien CELLE