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; } } }

An error has occurred while trying to access HOPI

System

This error happens randomly. Today I was trying to generate a page. Other times I have been trying to edit a tpl

Find more posts tagged with

Comments

wscott

You should probably contact Interwoven Support. If this is a known issue they can help you sort it out very quickly, and if this is a new issue they can get you in touch with the right people to help debug and correct it.

flivauda

HOPI and TPLs are outside the scope of LiveSite, so I'm not sure how you'd be getting this error thru LiveSite. Will is correct, you should contact support on this issue, or post on the TS forum.

rabs

This might help...........

Synopsis
This article explains how to change or add local privileges on the TeamSite server to correct the HOPI error issues.
Details

There are two set of security policies in Windows, Allow log on locally and Deny log on locally. TeamSite maintains user to group mappings in the cache to grant or deny access to the shared assets. These mappings are maintained for all the users listed in the TeamSite roles files. The list of user to group mapping is updated every 10 minutes, by default. To avoid the HOPI error, you need to make sure the user or the group has log on locally privileges. Also, check the Deny log on locally to make sure there is not a user or group you need blocked.

You can safely delete the “SUPPORT_388945a0" user on Windows 2003 Logon Locally Policy.

Steps: Go to administrative Tools, Local Security Policies, User Rights and Assignment, “Allow log on locally”

Troubleshooting Tips:

Check your local user and group section to make sure you have your member on the group.
Get the “iwutild.log” located on “\iw-home\local\logs” to check for errors.

Bjorn

We've been talking to IW Support about this and they've said the same thing you have. But is it then safe to say that in order to use the full feature set of the product (in our case, TeamSite) -- that EACH AND EVERY user needs to have "logon locally" access on that server?