Well I looked at that post, Jim was installing on a DNN4.8, he had a different issue.
If I read this right, you installed the latest IFRAME module on a DNN4.03. Big Problem I'm guessing.
The stored procedure its telling you it cant find is for a token replacment system for profile data in a querystring params option of the module (I think) its a storeprocedure that wouldnt have existed until 4.3.3 when the profile was modified to the new profile provider, this module is depending on.
I'm guessing errors can only be seen on the localhost, so thats why you need your host to provide you with the error....(yikes the luxury of having servers in house)
I wonder if you have the tools needed to fix this.
I'm sure some guru knows an easier fix.....
If it were me, I would have backup everything before I began. And restored everything from backups if things went wrong, and they went wrong.....
But had you done that your post would be slightly different.
Installing this module did a few things to your codebase and database, all of which can be reversed.
But with the tools you have I dont think you can fix it. You're at the mercy of the host to fix it.
To fix this I would need access to the file system and the database, both of which your host has a monopoly on right now.
If it were me I would look at the SQL install script the IFRAME ran, remove the wrong version iframe files added during install, add the correct version files, run a SQL script to 'reverse' what the install SQL script did.
But then again if it were me I would have backed it up first =D
Good Luck.