I am trying to use report caster to schedule a report to be emailed everry morning. When I select this report in task and try to schedule it, I get error messagge invalid credential. Is this user permissions realted error or something is wrong with the report:

I am able to schedule other report
I am able to run this report directly from report painter or public dashboard.

This message has been edited. Last edited by: Kerry,

Check the execution id and password you are using for the schedule. Is it locked or invalid?

I am getting the following error when I try to schedule this report:

server disconnected, cause 32033 eda state-17

That's a bad password. Did the password get changed? Do you know what it is? To fix, click the password button next to the execution id in the task and fix the password. That will fix it for all schedules that use that id.

That is actually a bad userid, not a bad password:

http://documentation.informati...sgcode_71/20msg2.htm

A bad password is a 32034.

However, Ginny is right that error is from the Reporting Server. As a result it means your userid is bad for the execution id you're using.

Because I changed the windows password and report caster saves password in caster DB, I had to change the password in caster composer.

Arif

From the messages and codes manual:

quote:

-17 Invalid user ID or password.

In his case it was the password.

Arif, when you change the opsys password, you must change the password in at least one of the schedules using that id. That will reset it for all jobs using that execution id.

-17 is a generic message that is accompanied with several types of failure. Its the EDA code that gives you more specifics as to what type of failure that is, e.g 32033.

The code 32033 means an invalid userid, not an invalid password. An invalid password is a 32034.

The only exception I can think of is with a Reporting Server set to LDAP with a service account, all failures are returned as a "Userid failuer" 32033.

This is because the service account is used for the connection to LDAP, therefore essentially the only thing being checked is the userid and what the failure came from is not clear.