cancel
Showing results for 
Search instead for 
Did you mean: 

Some frames are not loaded in the Portal

Former Member
0 Kudos

Hi,

We have problems loading some images into the portal. Rather than display properly, an error type 503 but sometimes loads properly. These images are loaded from the KM repository, checking the log default_ * trc see this error message related to the table "KMC_DBRM_CONTTRACK":

#1.5 #005056866EFF008C0000267600000D0C00049748A43048DF#1292238154863#com.sap.sql.jdbc.direct.DirectPreparedStatement#sap.com/irj#com.sap.sql.jdbc.direct.DirectPreparedStatement#jpenaranda#88002##n/a##7762540006a811e0c3ca005056866eff#SAPEngine_Application_Thread[impl:3]_43##0#0#Error#1#/System/Database/sql/jdbc/direct#Java#com.sap.sql_0003##SQL

error occurred on connection MAD-EP-BD-01:EPP:SAPEPPDB: code=1,205,

state="40001", message="[NWMss37][SQLServer JDBC

Driver][SQLServer]Transaction (Process ID 63) was deadlocked on lock

resources with another process and has been chosen as the deadlock

victim. Rerun the transaction.";

SQL statement is "UPDATE "KMC_DBRM_CONTTRACK" SET "REFCOUNT" = "REFCOUNT"

+ 1 WHERE "ID" = 0".

[EXCEPTION]

#6#1205#40001#[NWMss37][SQLServer JDBC Driver][SQLServer]Transaction(Process ID 63) was deadlocked on lock resources with another process and

has been chosen as the deadlock victim. Rerun the

transaction.#MAD-EP-BD-01:EPP:SAPEPPDB#UPDATE "KMC_DBRM_CONTTRACK" SET

"REFCOUNT" = "REFCOUNT" + 1 WHERE "ID" = 0#java.sql.SQLException:

[NWMss37][SQLServer JDBC Driver][SQLServer]Transaction (Process ID 63)

was deadlocked on lock resources with another process and has been chosen

as the deadlock victim. Rerun the transaction.

Please, if anyone has had this problem and could fix it, would appreciate any information.

Thanks,

Regards.

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi,

SAP told us a workaround and this has solved the problem. The workaround is the follow:

You must disable the tracking content in the repositories used, this is explained in note 900571, section D.

D) Content Tracking of the CM store in persistence mode FSDB.

After disabling this option and restart the j2ee, images are viewed without problem again as well as other documents that are stored in KM

Thanks,

Regards.

Former Member
0 Kudos

Hi,

Thanks for your reply. I checked the list of locked objects but is empty. We restarted the J2EE, SQL Server and server but the error message persists.

Regards

Former Member
0 Kudos

Can you restart the host as well as I see that there is a conflict at the OS level with processes accessing this?

Former Member
0 Kudos

Go to System Monitoring->under portal select object locking and see if there are any objects locked there. Delete the locks and see if that works.