Error message: a problem connecting to the server "DriveMap"

Question

I recently uninstalled GoDaddy’s software Workspace, used to manage online storage which I no longer need. Every time I restart my computer, and worse, every time I update an app, put something in the trash, or empty the trash, I get the error message “There was a problem connecting to the server "DriveMap". Workspace (DriveMap) is no longer on my computer; I used GoDaddy’s Workspace uninstaller to remove it. Then I reinstalled and uninstalled again because I was getting that message. I then did a search of my computer for all files with “Starfield” in the title, which is the developer of WorkSpace. I found about a dozen files and deleted them. I’m still getting the message, and GoDaddy support is absolutely useless. I got this reply from them (their 15th reply about this problem).
It appears that your computer is configured to open a drive, which is occurring during start up.  You will need to edit your computer's drives or start up commands and delete the command that is causing this to occur.  This would not be a file that from Workspace that is causing the issue.  It appears that your local system is still trying a program that no longer exists on the system.  We suggest researching support documentation related to your local system to remove the DriveMap. 
It has to be a file from Workspace, it seems to me, or a system file that has been altered by Workspace. This didn’t happen before I installed Workspace. It started happening out of the blue... hadn’t added any files to online storage or accessed my online file folder for a month or more, and this event began occurring, at times rendering my computer unusable; that message pops up as fast as I can dismiss it, many many times... Intercepts all key strokes.
I’ve looked at my account’s startup items; nothing there. And iMacHardDisk/Library/Startupitems has only a backup program in it.
Has anyone had this problem and found a fix?

Answer 1

Please read this whole message before doing anything.
This procedure is a diagnostic test. It won’t solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
Third-party system modifications are a common cause of usability problems. By a “system modification,” I mean software that affects the operation of other software — potentially for the worse. The following procedure will help identify which such modifications you've installed. Don’t be alarmed by the complexity of these instructions — they’re easy to carry out and won’t change anything on your Mac.
These steps are to be taken while booted in “normal” mode, not in safe mode. If you’re now running in safe mode, reboot as usual before continuing.
Below are instructions to enter some UNIX shell commands. The commands are harmless, but they must be entered exactly as given in order to work. If you have doubts about the safety of the procedure suggested here, search this site for other discussions in which it’s been followed without any report of ill effects.
Some of the commands will line-wrap or scroll in your browser, but each one is really just a single line, all of which must be selected. You can accomplish this easily by triple-clicking anywhere in the line. The whole line will highlight, and you can then either copy or drag it. The headings “Step 1” and so on are not part of the commands.
Note: If you have more than one user account, Step 2 must be taken as an administrator. Ordinarily that would be the user created automatically when you booted the system for the first time. The other steps should be taken as the user who has the problem, if different. Most personal Macs have only one user, and in that case this paragraph doesn’t apply.
Launch the Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ If you’re running OS X 10.7 or later, open LaunchPad. Click Utilities, then Terminal in the page that opens.
When you launch Terminal, a text window will open with a line already in it, ending either in a dollar sign (“$”) or a percent sign (“%”). If you get the percent sign, enter “sh” and press return. You should then get a new line ending in a dollar sign.
Step 1
Copy or drag — do not type — the line below into the Terminal window, then press return:
kextstat -kl | awk '!/com\.apple/{printf "%s %s\n", $6, $7}'
Post the lines of output (if any) that appear below what you just entered (the text, please, not a screenshot.) You can omit the final line ending in “$”.
Step 2
Repeat with this line:
sudo launchctl list | sed 1d | awk '!/0x|com\.(apple|openssh|vix)|edu\.mit|org\.(amavis|apache|cups|isc|ntp|postfix|x)/{print $3}'
This time, you'll be prompted for your login password, which won't be displayed when you type it. You may get a one-time warning not to screw up. You don't need to post the warning.
Note: If you don’t have a login password, you’ll need to set one before taking this step. If that’s not possible, skip to the next step.
Step 3
launchctl list | sed 1d | awk '!/0x|com\.apple|edu\.mit|org\.(x|openbsd)/{print $3}'
Step 4
ls -1A /e*/mach* {,/}L*/{Ad,Compon,Ex,Fram,In,Keyb,La,Mail/Bu,P*P,Priv,Qu,Scripti,Servi,Spo,Sta}* L*/Fonts 2> /dev/null
Important: If you formerly synchronized with a MobileMe account, your me.com email address may appear in the output of the above command. If so, anonymize it before posting.
Step 5
osascript -e 'tell application "System Events" to get name of every login item' 2> /dev/null
Remember, steps 1-5 are all drag-and-drop or copy-and-paste, whichever you prefer — no typing, except your password. Also remember to post the output.
You can then quit Terminal.