Hello.
I am getting this error when AutoSPInstaller attempts to install SharePoint 2013 on remote Windows 2012R2 servers:
- Starting remote session to SERVER2...
- SharePoint 2013 binaries are not yet installed on SERVER2.
- Launching AutoSPInstaller...
The term '\\server1\AutoSPInstaller\SP\AutoSPInstaller\AutoSPInstallerMain.ps1' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
+ CategoryInfo : ObjectNotFound: (\\server1...stallerMain.ps1:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
+ PSComputerName : SERVER2
- Removing session "AutoSPInstallerSession-SERVER2..."
I have tried the suggestions in the documentation but they have not worked for me. Has anybody else encountered and resolved this issue? I can manually browse to the script on server1 from server2 so I know it's accessible.
Comments: ** Comment from web user: brianlala **
I am getting this error when AutoSPInstaller attempts to install SharePoint 2013 on remote Windows 2012R2 servers:
- Starting remote session to SERVER2...
- SharePoint 2013 binaries are not yet installed on SERVER2.
- Launching AutoSPInstaller...
The term '\\server1\AutoSPInstaller\SP\AutoSPInstaller\AutoSPInstallerMain.ps1' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
+ CategoryInfo : ObjectNotFound: (\\server1...stallerMain.ps1:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
+ PSComputerName : SERVER2
- Removing session "AutoSPInstallerSession-SERVER2..."
I have tried the suggestions in the documentation but they have not worked for me. Has anybody else encountered and resolved this issue? I can manually browse to the script on server1 from server2 so I know it's accessible.
Comments: ** Comment from web user: brianlala **
I've seen this happen before when User Access Control is enabled (default) and you have not tried to connect to the share with an Administrator-level token. To test this, you can open a command prompt as administrator from each machine in the farm, and do a __net use '\server1\AutoSPInstaller\SP\AutoSPInstaller\AutoSPInstallerMain.ps1'__.
BTW, I notice a missing \ slash at the start of your path above, assuming it's just a typo when you pasted/typed the error details? If not then this is likely the cause of your issue.
Brian