Automator not saving server's name in "Get Specific Server" action

Question

Automator not saving server's name in "Get Specific Server" action

I just upgraded to Lion and realized that the Automator actions that used to work with Snow Leopard are no longer working.

I created an automation application and put it in the "log in item" to mount servers when I started the computer.

With Lion, I could not save the specified smb://* address in the action. Although I could run and test it in the automator, the specified smb://* would be gone when I reopened the application in Automator.

Strangely enough, one of the similar Automator applications was able to retain the two smb://* addresses when I open the application in Automator. This application was created in my prior Snow Leopard machine. However this application will not let me save any new smb://* in addition to the two.

Any idea what is happening?

MacBook Pro, Mac OS X (10.7), Automator

Posted on Aug 14, 2011 1:59 PM

Reply

Answer 1

Uyzer

Level 1

4 points

Aug 17, 2011 6:11 PM in response to tenspiderfingers

I have the same problem with Automator on my MacBook Air running Lion. It doesn't save my smb server names.

Reply

Answer 2

MacRob14

Level 1

0 points

Aug 27, 2011 10:28 PM in response to Uyzer

I found that you can just go to your user settings a login items, click the + and then navigate to the folder or server you want to add when you login/startup and then click Add in the dialogue box and it will use that to add that folder or server now instead of using the automator process. Hope this helps.

Reply

Answer 3

Aug 30, 2011 10:56 PM in response to tenspiderfingers

Same problem here as well! the get server function saved the smb:// path for a minute but when save and reopened the path is gone.

Does anybody else have any solutions? I'm not always connect to the specified network and i'd rather not have to deal with the unable to connect messages at startup.

Reply

Answer 4

Aug 30, 2011 11:14 PM in response to tenspiderfingers

After much reading and research on the internet, I find the following solution.

Do not use the Automator script "Get Specified Server"

Instead use "Run Apple Script" under Utilities

Put in the following script

on run {input, parameters}

tell application "Finder"

try

mount volume "smb://****"

end try

end tell

return input

end run

Save as a service in the Automator service folder. You can access it from the contextual menu by control+click.

Hope this help.

Reply

Answer 5

Aug 31, 2011 6:42 AM in response to tenspiderfingers

Looks like a solid work around!

Thanks!

Reply

Answer 6

Uyzer

Level 1

4 points

Aug 31, 2011 6:44 AM in response to tenspiderfingers

Works like a charm...thanks!

Reply

Answer 7

n_m_w

Level 1

10 points

Jan 1, 2012 7:21 PM in response to tenspiderfingers

To address original bug in Automator ...

1. Create/ update your mount application in Automator (add URL's for servers/ drives to mount) - save version

2. Open/ view the package contents of this new application/ version (via right click context menu of application > 'Show Package Contents')

3. Manually edit the document.wflow file (within the contents folder of the opened package) with TextEdit (via context menu of document.wflow file > 'Open with'), adding bold/ italic entries as per below for relevant mount points where the information is missing..

<key>ActionName</key>

<string>Get Specified Servers</string>

<key>ActionParameters</key>

<dict>

<key>items</key>

<array>

<dict>

<key>kind</key>

<string>server</string>

</dict>

</array>

</dict>

4. Save new version of document.wflow

After making these corrections the application should work correctly, and when opening directly in Automator the 'Get Specified Server' list should correctly show all mount points within the list view.

You can then add this application to a users login items to run @ login and mount required volumes without annoying mount popups

Regards

Neil

Reply

Answer 8

Jul 24, 2012 9:30 AM in response to n_m_w

Thanks, that's much better than a workaround.

Reply