Solved Unable to mark NAS location trusted in Office
-
@BraswellJay said in Unable to mark NAS location trusted in Office:
In our case the version of access being used was 2007 and I have to install the access 2007 runtime on each machine that runs the application. That also is where the 12.0 comes from in the registry key path. That may be different if the access version is not 2007.
Office 365 "always" up to date. but i'll go dig for that key.
-
@JaredBusch That is weird, both should have been allowed to do that.
-
@JaredBusch I had same problem recently. Solution was to use name instead of IP address.
I had to map folder as\\FILESERVER\Data -
@triple9 said in Unable to mark NAS location trusted in Office:
@JaredBusch I had same problem recently. Solution was to use name instead of IP address.
I had to map folder as\\FILESERVER\Dataas I noted in the OP, that did not work.Looks like I have to do the same.
-
@BraswellJay said in Unable to mark NAS location trusted in Office:
I have a similar issue with a 3rd party developed application that uses an access database. The only way I could find to workaround was to add the trusted location through a registry edit. Here is the notes I have on what I did
I was able to add
\\FileServer\Data\via the built in GUI, by clicking Add new location and then browsing to Network and clicking on the FileServer item, etc. This added the location like this. This works, as I can open the file and have no warning about disabled macros, but is a work around. The Mapped Drive should work also.
I then exported the key and tweaked it to add
K:\inLocation1.
No luck opening the file viaK:\does not work.
Even though it does show up in trust center after adding via the registry.
As a side note, I can not click on
K:\entry in the GUI either. I can click on the other two entries. -
-
@JaredBusch said in Unable to mark NAS location trusted in Office:
@BraswellJay said in Unable to mark NAS location trusted in Office:
I have a similar issue with a 3rd party developed application that uses an access database. The only way I could find to workaround was to add the trusted location through a registry edit. Here is the notes I have on what I did
I was able to add
\\FileServer\Data\via the built in GUI, by clicking Add new location and then browsing to Network and clicking on the FileServer item, etc. This added the location like this. This works, as I can open the file and have no warning about disabled macros, but is a work around. The Mapped Drive should work also.
I then exported the key and tweaked it to add
K:\inLocation1.
No luck opening the file viaK:\does not work.
Even though it does show up in trust center after adding via the registry.
As a side note, I can not click on
K:\entry in the GUI either. I can click on the other two entries.Just a WAG, but what if you map K:\ to \Fileserver and then trust K:\data folder. Maybe it wants a specific folder verses an entire drive?
-
@JaredBusch said in Unable to mark NAS location trusted in Office:
@BraswellJay said in Unable to mark NAS location trusted in Office:
I have a similar issue with a 3rd party developed application that uses an access database. The only way I could find to workaround was to add the trusted location through a registry edit. Here is the notes I have on what I did
I was able to add
\\FileServer\Data\via the built in GUI, by clicking Add new location and then browsing to Network and clicking on the FileServer item, etc. This added the location like this. This works, as I can open the file and have no warning about disabled macros, but is a work around. The Mapped Drive should work also.
I then exported the key and tweaked it to add
K:\inLocation1.
No luck opening the file viaK:\does not work.
Even though it does show up in trust center after adding via the registry.
As a side note, I can not click on
K:\entry in the GUI either. I can click on the other two entries.is K mapped with a name or an IP?
-
@Dashrender said in Unable to mark NAS location trusted in Office:
is K mapped with a name or an IP?
By IP.
I assume it will work when I remap it with the DNS entry.
-
@JaredBusch said in Unable to mark NAS location trusted in Office:
@Dashrender said in Unable to mark NAS location trusted in Office:
is K mapped with a name or an IP?
By IP.
I assume it will work when I remap it with the DNS entry.
Had this same issue, had to map via dns name rather than ip address.
Microsoft claims this is a feature.
-
@DustinB3403 said in Unable to mark NAS location trusted in Office:
@JaredBusch said in Unable to mark NAS location trusted in Office:
@Dashrender said in Unable to mark NAS location trusted in Office:
is K mapped with a name or an IP?
By IP.
I assume it will work when I remap it with the DNS entry.
Had this same issue, had to map via dns name rather than ip address.
Microsoft claims this is a feature.
Except this worked until 2 weeks ago by IP. So fuck you Microsoft.
user is supposed to be back int he office Thursday, so I can test this.
-
@JaredBusch I get it, 100%.
I had a customers entire production shop (who actually has public IP address subnet for their LAN) who came to a complete halt calling in for assistance in sorting out what the hell happened.
Microsoft claimed this was a security feature. . .
-
@JaredBusch Any update?
-
@DustinB3403 said in Unable to mark NAS location trusted in Office:
@JaredBusch Any update?
Waiting on the user to schedule time.
-
@JaredBusch said in Unable to mark NAS location trusted in Office:
@DustinB3403 said in Unable to mark NAS location trusted in Office:
@JaredBusch Any update?
Waiting on the user to schedule time.
the best part, waiting. . . lol
Well have a good weekend.
-
J JaredBusch has marked this topic as solved on
-
Tested and it works all the time by hostname instead of IP.
