# TypeError: Cannot read property 't' of undefined

**URL:** <https://discourse.nodered.org/t/typeerror-cannot-read-property-t-of-undefined/27557>\
**Category:** General\
**Created:** [31 May 2020 06:59 UTC](https://discourse.nodered.org/t/typeerror-cannot-read-property-t-of-undefined/27557 "2020-05-31T06:59:47Z")\
**Posts on this page:** 2\
**Page:** 2

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [11 June 2020 14:46 UTC](https://discourse.nodered.org/t/typeerror-cannot-read-property-t-of-undefined/27557/21 "2020-06-11T14:46:20Z")

</div>

So the share has different user access control to the account running node red.

One way to resolve this is, create a service account & run node re under that account.  
Then make sure the service account if permitted to access the share.

Alternatively, try [node-red-contrib-smb](https://flows.nodered.org/node/node-red-contrib-smb) - I havent tried it myself (as our service accounts that run node-red are domain accounts that have access to the shared resource - meaning the file node just works)

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [10 August 2020 14:46 UTC](https://discourse.nodered.org/t/typeerror-cannot-read-property-t-of-undefined/27557/22 "2020-08-10T14:46:27Z")

</div>

Closed on 10 August 2020 14:46 UTC

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.

[Previous page](https://discourse.nodered.org/t/typeerror-cannot-read-property-t-of-undefined/27557.md?page=1)