When setting up your script schedule, are you certain that that account name and password are exactly correct including caps?
Yes, I have check, re-checked, and checked again that the user name and password are typed correctly.
Check the account privileges for your account.
Is it a full access account? You shouldn't need a full access account, but you might want to specify a full access account as a quick test to see if it's a privileges issue.
Yes, as I stated in my original post, I am using my full access account.
You stated in your initial post that you "have full access". I wanted to be sure that you were using your "full access" account in your script schedule. The only thing left that occurs to me is to try testing a recovered copy of the file. You might have some hidden file corruption.
This isn't much help but thought I'd add a 'me too' post.
I had a script schedule which was running fine and went to edit it in the Console and after a few minutes of no response received 'No scripts are available for the specified account'.
I've since tried rebooting and instead using the admin account/password on a number of databases, all with the same result.
Windows Server 2003.
This is now working for us.
I've just upgraded our virtual server from 500 Megs to 2 Gigs of RAM and can now edit the schedule.
(I know 500 Megs is less than the 1 Gig minimum in the specs but Windows Task Manager was only ever showing about 25% page file usage.)