"An item with this name already exists"

"An item with this name already exists"

  • Comments 1
  • Likes
SYMPTOMS
When you try to re-publish a briefing book in ProClarity Desktop Professional or in ProClarity Web Professional, you receive the following error message:
An item with this name already exists.
Additionally, you may experience the following symptoms:
When you delete a book in Desktop Professional, you receive OLE exception 80040e21.
When you delete a My Views folder or item, you receive exception 80040e21 in the ProClarity Event Log.
When you delete or modify security roles in the Administrator Tool, you receive OLE exception 80040e21.
CAUSE
This issue may occur if the name of the computer that is running Microsoft SQL Server has changed. ProClarity Analytics Server uses a database in SQL Server to store information about the users, the queries, and the server configurations.
RESOLUTION
Note To verify the internal information about the computer name, run the following SQL queries.
select @@servername
 
USE master; 
GO 
EXEC sp_helpserver 

If the values that are returned by the queries are not identical, you are experiencing the issue that is mentioned in the "Symptoms" section. To resolve this issue, follow these steps:
1. Run the following command to clear out existing server name information.
sp_dropserver @server = '<serverName>' 
2. Run one of the following commands to add the correct name of the server.

Note To find the correct local server name, click Start, right-click My Computer, and then click the Computer Name tab.
sp_addserver '<machineName>\<instanceName>', local 
sp_addserver '<machineName>', @local= 'local' 
3. Restart the SQL service.
4. Restart the IIS service on the computer that is running ProClarity Analytics Server.
5. Restart ProClarity Professional, and then retest publishing.
Comments
  • Here's another take on the same fix:

    CAUSE:

    Machines were being re-imaged and the name of the SQL Server in the image didn't always match the computer / server name. When there was a mis-match

    linked server queries to the machine would fail since they were going out to the OLE DB provider which couldn't find the server name.

    RESOLUTION:

    Make sure that the computer / server name and the SQL Server name match.

    -- check that the output of this query is the same as your computer name

    select @@servername

    -- if @@servername does not match your computer name, then execute these steps

    --- backup master ....

    exec sp_helpserver -- to see what you have now

    exec sp_dropserver 'ResultsOfServerName'

    exec sp_dropserver 'YourMachineName'

    exec sp_addserver 'YourMachineName', 'local'

    exec sp_helpserver -- to see what you have after the changes

    -- restart SQL Server

    Example:

    -- Computer/machine name is CurrentComputer

    -- select @@servername returns DifferentComputer

    -- backup master --

    exec sp_helpserver

    exec sp_dropserver 'DifferentComputer'

    exec sp_dropserver 'CurrentComputer'

    exec sp_addserver 'CurrentComputer', 'local'

    exec sp_helpserver

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment