Section Access issues on new cluster

[#1]

I am pretty new to QV and have had a few people help out on our installation, but we are stuck. We have our production document running and loading on our production server, QV1. Our test server, QV3, also loads a copy of this doc without issue. QV3 has our Publisher installed, and distributes docs to our test domain on QV3, and our new cluster boxes. Our production doc has been copied to the cluster, but there are issues with user access. If we have Strict Exclusion checked, then only Admin users can get to the doc. If Strict Exclusion is unchecked, then users have access, but to all of the data (the Section Access restrictions are not being applied).

Has anyone run into this, or something similar?

[Peter_Cammaert]

That's the normal effect of strict exclusion:

• Strict exclusion ON: if the current account causes all data to be reduced away, access to the document is denied.
• Strict exclusion OFF: if the current account causes all data to be reduced away, access is granted to the full document with all data in place.

Check SA in your production document. There must be something wrong with the accounts that are (not) recognized on production. Are ADMIN accounts builtin, and USER accounts loaded from some external source?

Peter

[#3]

Thank you for the reply Peter.

That is what is confusing about this - production works fine. Publishing to our test box works find (which is a copy of our production document. Our Publisher is on our test environment, which also publishes to our cluster, but when the doc is there is when it has issues. I've checked all the Services accounts, and they match up between our test box and our cluster boxes.

Strict Exclusion is checked, and functioning as expected, on production, too.

[Peter_Cammaert]

Can you add a text box containing =OSUser() to your document with Strict Exclusion disabled and publish it again on production? Then let a regular user open the AP document and report back what the text box says. 

Peter