nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Unable to see the attachment of all Task in workflow

JPR

Hi All,

I am unable see the attachment in all workflow.

And it is throwing the dm_portinfo as DM_QUERY_E_TABLE_NO_ACCESS,

But I had updated the permission for permit_group_world = 15, even though I am facing the same problem.

Please assit me if any one face the same.

Thanks in advance.

Jagadish Chadalavada

Find more posts tagged with

Comments

DCTM_Guru

You also need to verify the acl object assigned to registered table gives READ permissions to your user acct.

JPR

I do changed the permissions to Write Acl provided on User and even I had updated the permission on Register table to write.

Please assist me how can I debug this one. I am attaching the Log file.

DCTM_Guru

"The table, VN_PROD.dm_portinfo, is not registered or you do not have access to it."

Did you register the table (ie create dm_registered object for your table)? If so, I have seen where you have to delete the object and re-register it to get it working.

JPR

Hi Jonny,

Is it possible to re-register dm_portinfo table ? . But this table is not present in data base, it was in \System\ Cabinet.....

Please help to re-register this table.

Thanks,

Jagadish

DCTM_Guru

Delete the dm_registered object that corresponds to this table re-execute the register DQL.

JPR

Hi Jonny,

I had re-register the table with the following way,

register table dm_dbo.dm_portinfo(r_object_id char(16), r_port_name char(16), r_port_type char(16), r_package_name char(128), r_package_type char(40), r_package_oprtn char(64), r_package_id char(16), r_package_label char(32), r_package_flag char(0), r_condition_name char(16), r_condition_port char(16));

And it was worked. Having a doubt whether I can ask you or not I dont know but, generally these default table is registered by the Docbase service / schema owner it self, if we do it externally, do we face any issues in future?

Thanks.. Jagadish

DCTM_Guru

I never heard of dm_portinfo and its not in the object reference manual, so I presumed that this is custom table, which is why you need to manually register the table yourself. You are correct that system tables are normally "registered" during installation, but since this isnt a system table, you need to manually register it.

PK4D

We ran into the exact same problem recently, and arrived at the permissions on the dm_registered object for dm_portinfo as the cause of the problem. We fixed the problem by editing the ACL associated with the object and giving READ to the world.

We still don't know how the problem came about as it was a 5.3 SP6 docbase clone upgraded to 6.6. The problem doesn't exist in the original docbase - world has read on the dm_registered and the interaction with tasks has no problems in the original docbase.

This is the first time for me as well in dealing with dm_portinfo - definitely nothing custom about it.

PK4D

Not sure if it is related but I found vaguely similar problems with dm_portinfo registration reported over 6 years ago on various forums. Just Google it.

Johnny, I found your posts in one of those threads as well

DCTM_Guru

Got of love EMC documentation. Glad to hear you got the problem fixed.