Dexterity runtime error - you do not have permission to open this

[kathyh]

I am receiving a Dexterity runtime error - you do not have permission to open
this file when attempting to launch enterprise. The whole company is having
this problem. I do not believe any changes have been made to the system. What
would cause this error?

[Victoria [MVP]]

The last time I encountered this there was a problem with the reports.dic.
It's either a permissions/access issue (the file is not available) or the
file got corrupted (this sometimes happens when reports are imported or
edited while other users are in Great Plains). You can try pointing to a
local reports.dic as a test to troubleshoot this.

There are a couple of KB articles that I found that may also help:

KB 865521
KB 843755
--
Victoria Yudin
Microsoft MVP - Great Plains

Post by kathyh
I am receiving a Dexterity runtime error - you do not have permission to open
this file when attempting to launch enterprise. The whole company is having
this problem. I do not believe any changes have been made to the system. What
would cause this error?

[GPaddict]

Hello Victoria,

We are experiencing similar issues attempting to share the reports
dictionary over the network (Dexterity Runtime - Unknown dictionary error). I
wanted to review the article posts you included in your message but I can't
find the articles through the knowledge base. I tried searching using the
following URL:
http://support.microsoft.com/?kbid=n but I receive this message
"The Knowledge Base (KB) Article You Requested Is Currently Not Available"
Perhaps I require additional permission?????

Accessing reports.dic locally works fine but it defeats the purpose. Could
you pls advise on how I could access the articles you specified?

Thanks,

Joel

Post by Victoria [MVP]
The last time I encountered this there was a problem with the reports.dic.
It's either a permissions/access issue (the file is not available) or the
file got corrupted (this sometimes happens when reports are imported or
edited while other users are in Great Plains). You can try pointing to a
local reports.dic as a test to troubleshoot this.
KB 865521
KB 843755
--
Victoria Yudin
Microsoft MVP - Great Plains

Post by kathyh
I am receiving a Dexterity runtime error - you do not have permission to open
this file when attempting to launch enterprise. The whole company is having
this problem. I do not believe any changes have been made to the system. What
would cause this error?

[Victoria [MVP]]

Joel,

Do you have access to CustomerSource? Here is the link to the MBS specific
are of the MS KnowledgeBase:
https://mbs.microsoft.com/knowledgebase/search.aspx and it will use your
CustomerSource login.

To address your question on the reports.dic - if the same file is working
fine locally, but not shared on a network, then most likely it's a
permissions issue. The user accessing the shared reports.dic needs to have
full control of the file.
--
Victoria Yudin
Microsoft MVP - Great Plains

Post by GPaddict
Hello Victoria,
We are experiencing similar issues attempting to share the reports
dictionary over the network (Dexterity Runtime - Unknown dictionary error). I
wanted to review the article posts you included in your message but I can't
find the articles through the knowledge base. I tried searching using the
http://support.microsoft.com/?kbid=n but I receive this message
"The Knowledge Base (KB) Article You Requested Is Currently Not Available"
Perhaps I require additional permission?????
Accessing reports.dic locally works fine but it defeats the purpose. Could
you pls advise on how I could access the articles you specified?
Thanks,
Joel

Post by Victoria [MVP]
The last time I encountered this there was a problem with the
reports.dic.
It's either a permissions/access issue (the file is not available) or the
file got corrupted (this sometimes happens when reports are imported or
edited while other users are in Great Plains). You can try pointing to a
local reports.dic as a test to troubleshoot this.
KB 865521
KB 843755
--
Victoria Yudin
Microsoft MVP - Great Plains

Post by kathyh
I am receiving a Dexterity runtime error - you do not have permission to open
this file when attempting to launch enterprise. The whole company is having
this problem. I do not believe any changes have been made to the
system.
What
would cause this error?

[GPaddict]

Hi Victoria,

Thanks for the quick response ...
I will try accessing Customer Source. Initially I failed to access, but that
was before I registered. It is related to permissions then. I will review the
rights/privileges of the network path.

Thanks a million ...
I just joined the community and I'm already impressed (-;

Regards, Joel

Post by Victoria [MVP]
Joel,
Do you have access to CustomerSource? Here is the link to the MBS specific
https://mbs.microsoft.com/knowledgebase/search.aspx and it will use your
CustomerSource login.
To address your question on the reports.dic - if the same file is working
fine locally, but not shared on a network, then most likely it's a
permissions issue. The user accessing the shared reports.dic needs to have
full control of the file.
--
Victoria Yudin
Microsoft MVP - Great Plains

Post by GPaddict
Hello Victoria,
We are experiencing similar issues attempting to share the reports
dictionary over the network (Dexterity Runtime - Unknown dictionary error). I
wanted to review the article posts you included in your message but I can't
find the articles through the knowledge base. I tried searching using the
http://support.microsoft.com/?kbid=n but I receive this message
"The Knowledge Base (KB) Article You Requested Is Currently Not Available"
Perhaps I require additional permission?????
Accessing reports.dic locally works fine but it defeats the purpose. Could
you pls advise on how I could access the articles you specified?
Thanks,
Joel

[ERoss]

Victoria -

I am having same issue -

The users all have full modify rights on the share



In article <***@TK2MSFTNGP15.phx.gbl>, ***@flex-
solutions.com says...

Post by Victoria [MVP]
Joel,
Do you have access to CustomerSource? Here is the link to the MBS specific
https://mbs.microsoft.com/knowledgebase/search.aspx and it will use your
CustomerSource login.
To address your question on the reports.dic - if the same file is working
fine locally, but not shared on a network, then most likely it's a
permissions issue. The user accessing the shared reports.dic needs to have
full control of the file.

[Victoria [MVP]]

Did you look at those KB articles I mentioned in an earlier post? They cite
some other things to check....

Does it work if you copy the reports.dic from the share to a workstation and
point the GP instance on that workstation to the local file?
--
Victoria Yudin
Microsoft MVP - Great Plains

Post by ERoss
Victoria -
I am having same issue -
The users all have full modify rights on the share
solutions.com says...

Post by Victoria [MVP]
Joel,
Do you have access to CustomerSource? Here is the link to the MBS specific
https://mbs.microsoft.com/knowledgebase/search.aspx and it will use your
CustomerSource login.
To address your question on the reports.dic - if the same file is working
fine locally, but not shared on a network, then most likely it's a
permissions issue. The user accessing the shared reports.dic needs to have
full control of the file.

[ERoss]

I cannot access the ones you mentioned - but regular technet article
below was tried - yes copying reports.dic locally works -

But that is just a work around - makes backup & version control
difficult (we are ISO 9000 so version control is mandatory)


==================

CAUSE

Cause 1

The Dynamics.set file may be damaged. See Resolution 1 in the
"Resolution" section.


Back to the top


Cause 2

The Dynamics.set file may contain an incorrect path of a dictionary
file. See Resolution 2 in the "Resolution" section.


Back to the top


Cause 3

A dictionary that is referenced in the Dynamics.set file may be marked
as read-only. See Resolution 3 in the "Resolution" section.


Back to the top


Cause 4

A folder where a dictionary file is located may have incorrect
permissions settings. The dictionary file is referenced in the
Dynamics.set file. See Resolution 4 in the "Resolution" section.


Back to the top


RESOLUTION

Resolution 1

Re-create the Dynamics.set file.

For the steps to re-create the Dynamics.set file, click the following
article number to view the article in the Microsoft Knowledge Base:

850403 How to recreate the Dynamics.set file


Back to the top


Resolution 2

1.
Locate the Dynamics.set file. By default, this file is located in the
following folder:

C:\Program Files\Microsoft Business Solutions\Great Plains\

2.
Right-click the Dynamics.set file, and then click Properties.

3.
Verify that all paths that are listed for the dictionary files are
correct. Then make sure that you can open all the listed folders.





Back to the top


Resolution 3

1.
Locate the Dynamics.set file. By default, this file is located in the
following folder:

C:\Program Files\Microsoft Business Solutions\Great Plains\

2.
Right-click the Dynamics.set file, and then click Properties.

3.
Note the locations for all dictionary files.

4.
Verify the properties of each dictionary file. To do this, right-click
the file, and then click Properties.

5.
If a dictionary file is marked as read-only, clear the read-only
attribute and then click OK.





Back to the top


Resolution 4

1.
Locate the Dynamics.set file. By default, this file is located in the
following folder:

C:\Program Files\Microsoft Business Solutions\Great Plains\

2.
Right-click the Dynamics.set file, and then click Properties.

3.
Note the locations for all dictionary files.

4.
Verify the permissions to the folder or the folders where the
dictionary files are located. To verify the permissions, right-click the
folder, click Properties, and then click the Security tab. Make sure
that the user or the user group that is receiving the error message from
the "Symptoms" section has full control.

Note If the dictionary file is located in a shared folder, also make
sure to verify the permissions on the share. To do this, right-click the
folder, click Properties, and then click the Sharing tab. Make sure that
the user or the user group that is receiving the error message from the
"Symptoms" section has full control.








In article <***@TK2MSFTNGP12.phx.gbl>, ***@flex-
solutions.com says...

Post by Victoria [MVP]
Did you look at those KB articles I mentioned in an earlier post? They cite
some other things to check....
Does it work if you copy the reports.dic from the share to a workstation and
point the GP instance on that workstation to the local file?

[Victoria [MVP]]

Copying the reports.dic locally is just a test. If it works, then the issue
is not a corrupt reports.dic but access to the file. Assuming the domain
admin has access to all files, can you try logging onto Windows as a domain
admin and seeing if you still get the error?
--
Victoria Yudin
Microsoft MVP - Great Plains

Post by ERoss
I cannot access the ones you mentioned - but regular technet article
below was tried - yes copying reports.dic locally works -
But that is just a work around - makes backup & version control
difficult (we are ISO 9000 so version control is mandatory)
==================
CAUSE
Cause 1
The Dynamics.set file may be damaged. See Resolution 1 in the
"Resolution" section.
Back to the top
Cause 2
The Dynamics.set file may contain an incorrect path of a dictionary
file. See Resolution 2 in the "Resolution" section.
Back to the top
Cause 3
A dictionary that is referenced in the Dynamics.set file may be marked
as read-only. See Resolution 3 in the "Resolution" section.
Back to the top
Cause 4
A folder where a dictionary file is located may have incorrect
permissions settings. The dictionary file is referenced in the
Dynamics.set file. See Resolution 4 in the "Resolution" section.
Back to the top
RESOLUTION
Resolution 1
Re-create the Dynamics.set file.
For the steps to re-create the Dynamics.set file, click the following
850403 How to recreate the Dynamics.set file
Back to the top
Resolution 2
1.
Locate the Dynamics.set file. By default, this file is located in the
C:\Program Files\Microsoft Business Solutions\Great Plains\
2.
Right-click the Dynamics.set file, and then click Properties.
3.
Verify that all paths that are listed for the dictionary files are
correct. Then make sure that you can open all the listed folders.
Back to the top
Resolution 3
1.
Locate the Dynamics.set file. By default, this file is located in the
C:\Program Files\Microsoft Business Solutions\Great Plains\
2.
Right-click the Dynamics.set file, and then click Properties.
3.
Note the locations for all dictionary files.
4.
Verify the properties of each dictionary file. To do this, right-click
the file, and then click Properties.
5.
If a dictionary file is marked as read-only, clear the read-only
attribute and then click OK.
Back to the top
Resolution 4
1.
Locate the Dynamics.set file. By default, this file is located in the
C:\Program Files\Microsoft Business Solutions\Great Plains\
2.
Right-click the Dynamics.set file, and then click Properties.
3.
Note the locations for all dictionary files.
4.
Verify the permissions to the folder or the folders where the
dictionary files are located. To verify the permissions, right-click the
folder, click Properties, and then click the Security tab. Make sure
that the user or the user group that is receiving the error message from
the "Symptoms" section has full control.
Note If the dictionary file is located in a shared folder, also make
sure to verify the permissions on the share. To do this, right-click the
folder, click Properties, and then click the Sharing tab. Make sure that
the user or the user group that is receiving the error message from the
"Symptoms" section has full control.
solutions.com says...

Post by Victoria [MVP]
Did you look at those KB articles I mentioned in an earlier post? They cite
some other things to check....
Does it work if you copy the reports.dic from the share to a workstation and
point the GP instance on that workstation to the local file?

[ERoss]

In article <***@TK2MSFTNGP10.phx.gbl>, ***@flex-
solutions.com says...

Post by Victoria [MVP]
Copying the reports.dic locally is just a test. If it works, then the issue
is not a corrupt reports.dic but access to the file. Assuming the domain
admin has access to all files, can you try logging onto Windows as a domain
admin and seeing if you still get the error?

Does Yes and No count ??? :-)

logging in as domain administrator allows it to run - as a test I added
one of the GP users to the Domain Admins AD security group - it still
did not work

[Victoria [MVP]]

What version of Great Plains are you on?
--
Victoria Yudin
Microsoft MVP - Great Plains

Post by ERoss
solutions.com says...

Post by Victoria [MVP]
Copying the reports.dic locally is just a test. If it works, then the issue
is not a corrupt reports.dic but access to the file. Assuming the domain
admin has access to all files, can you try logging onto Windows as a domain
admin and seeing if you still get the error?

Does Yes and No count ??? :-)
logging in as domain administrator allows it to run - as a test I added
one of the GP users to the Domain Admins AD security group - it still
did not work

[ERoss]

In article <#***@TK2MSFTNGP10.phx.gbl>, ***@flex-
solutions.com says...

Post by Victoria [MVP]
What version of Great Plains are you on?

Good Morning !

Version 8.00g34

[Victoria [MVP]]

Thanks. I was asking for that in case you were on an older version of GP
that needed GP users to be Local Admins, but GP 8.0 does not. The only
other thing I can think of is that there are other *.dic files that are
shared that would also need to have permissions changed?

It has to be some sort of permissions/file access issue and that's not
really my specialty..... Maybe you can post in the AD newsgroup to see if
anyone can give you a better idea of what to look for to make sure you have
the correct permissions set? Basically you need all GP users to have full
control of reports.dic and any other shared *.dic files you may have in your
setup.
--
Victoria Yudin
Microsoft MVP - Great Plains

Post by ERoss
solutions.com says...

Post by Victoria [MVP]
What version of Great Plains are you on?

Good Morning !
Version 8.00g34

[LITS]

Is the reports dictionary being shared? Perhaps the permissions have changed
for the shared folder containing the reports.dic. That would cause this error
when launching the software.

Post by kathyh
I am receiving a Dexterity runtime error - you do not have permission to open
this file when attempting to launch enterprise. The whole company is having
this problem. I do not believe any changes have been made to the system. What
would cause this error?