If you ran that under the IS user, then it may already be persistent. But that IS user isn't logging in the same way that a human would, so without trying something like that out, I wouldn't be sure that persistence works the same way. I googled (I think) "net use share" and read some things there; I'm not a Windows admin, who may be able to know for sure.
The key is to make sure that you're referencing T: in the FileInput node, not the \\SMB server name. If it works, and then works after a reboot (when I presume the IS auto starts), then you may not need any custom start script. If it doesn't work after the reboot, you may need that custom start up to ensure that the drive is mounted prior to IS starting.
------------------------------
Tony Hays
Senior IT Architect
IBM Global Services
Spokane WA
706-305-8487
------------------------------
Original Message:
Sent: Fri September 16, 2022 02:54 PM
From: Daniel Friberg
Subject: Connecting ACE 12 to a SMB share?
Thanks Tony,
When we run the command:
Net use t: -p [file://[ip]/%5bshare]\\[ip]\[share] /user:[ID] [password]
The -p is to make it persistent. I thought that this would be enough for it to be set prior to the IS starting. Any suggestions to how do we could configure "Net use" so that it is always run before the IS starts?
Regards,
Daniel
------------------------------
Daniel Friberg
Original Message:
Sent: Wed September 14, 2022 11:04 AM
From: Tony Hays
Subject: Connecting ACE 12 to a SMB share?
I think the only way this will work is to have the IS user run the net use command prior to starting the IS, and having the IS File Input node use the T: mount point (or whatever you decide to use at that point) to access the file/folder needed. Something like a custom start script basically.
------------------------------
Tony Hays
Senior IT Architect
IBM Global Services
Spokane WA
706-305-8487
Original Message:
Sent: Mon September 05, 2022 02:19 PM
From: Daniel Friberg
Subject: Connecting ACE 12 to a SMB share?
Hi,We have an on-premise ACE 12.0.0.2 (& MQ) running on Windows 2019 Data Center VM.
We are trying to use the ACE File Input & output nodes to connect to an SMB share. The share cannot have an AD-connection, so we are trying to connect using a local user account created on the SMB-share.
This works fine using the Windows user account that the integration servers are running under. From file explorer we can connect OK to the SMB-share by using "connect as another user". We have also setup a persistent connection for the SMB with another user account using:
Net use t: -p [file://[ip]/%5bshare]\\[ip]\[share] /user:[ID] [password]
But the integration server cannot connect, and we get this warning from Windows Event log:
( BK12.ONE001.default ) File node ''File Input'' in message flow ''INT1064_server_testing'' can not access directory ''\\xx.xxx.x.xx\yyyyyyyy''.
The file node failed to find the directory ''\\\xx.xxx.x.xx\yyyyyyyy''. Either the directory does not exist, or the integration node does not have permission to access it. The node will continue checking at every poll interval. Ensure that the input directory exists, and that its permissions are correctly set.
We noticed that the problem seems to be that the file nodes always use the Windows account & password that the IS is running under. If we create a local user on the SMB-share with the same user name, the account gets locked because of too many wrong password attempts. We have also tried restarting the IS-servers & Windows.
Have we maybe missed anything in our setup?
Is there a way to connect to a SMB file share with a different user than what the integration server is running under?
Any workarounds or pointers are very much appreciated.
Regards,
Daniel
------------------------------
Daniel Friberg
------------------------------