2

When I try to open a SDL Tridion content Publication I get the error below and the tree is not expanding.

I am getting this error every 10 sec in the event viewer. I have also checked that a domain user is already added to the SDLSearchUsers.

Where else I need to check this user that this is a correct user?

Note: We are using SDL Tridion 2013 SP1.

Unable to index item: tcm:229-2211391. Sending a request to the Search Engine at http://localhost:8983/tridion failed with the following response: The connection can not be authenticated.

Component: Tridion.ContentManager.Search.Indexing

Errorcode: 865

User: NT AUTHORITY\SYSTEM

I am getting the following error as well.

A database error occurred while executing Stored Procedure "EDA_PUBLICATIONS_GETLISTDATA". Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. The wait operation timed out

Component: Tridion.ContentManager.CoreService Errorcode: 831 User: NT AUTHORITY\NETWORK SERVICE

  • Can you try by adding the MTS User in the SDLSearchUsers group and also ensure that MTS User and NT AUTHORITY\SYSTEM have write access to the %Tridion_Home% directory (for sake of verification at least). – Pankaj Gaur Jun 3 '15 at 14:13
  • tcm:229-2211391 note the item id! Wouldn't rule out that the search issue is unrelated... – Bjørn van Dommelen Jun 3 '15 at 20:19
  • Updated my answer to include approach to resolve database timeout errors. – Hiren Kaku Jun 5 '15 at 6:42
2

If the issue is with the permission then you can easily identify that issue:

Browse url: http://<CM Server>:8983 and provide the user name / pwd configured for search, if you are able to login and see all the configuration then it is not permission issue.

If it is not the permission issue then try to run powershell command to re-index the items: Sync-TcmSearchIndex (Reference: Powershell to reindex)

For the database timeout error: Please get the tables used by the procedure re-indexed. We had similar issue when creating component corresponding schema dropdown was not getting populated and we were getting timeout errors.

  • I tried to check the permission issue and it seems fine. Don't have the access to run powershell so cannot do indexing. Can we do indexing from database side ? – Jitender sharma Jun 4 '15 at 10:03
  • What is the error that you are getting when running powershell? Are you running powershell on CM server? – Hiren Kaku Jun 4 '15 at 15:10
0

I have come across same issue and this can also happen due to Tridion CM database user properties got messed up.

How to Fix?

  • Logon to the SQL Server with "Tridion DB User"
  • Open the user properties of the CM database
  • Click on "Membership" and select the "db_owner" (Tick Mark)
  • Click "Ok"
  • Restart the Tridion DB services

Now verify, issue will get resolved.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.