I am making a call to GenerateReport with the following code.  I've hard-coded the connection string (so you can see it) to just what I got out of the MySlxData.CurrentConnection during a previous attempt.

<pre>            string pluginid;
            if (ReportsHelper.GetPluginId("Opportunity:Open Opportunities Summary", out pluginid))
                {
                WebReportingClass reporting = new WebReportingClass();
                IDataService datasvc = MySlx.Data.CurrentConnection;
                IUser user = MySlx.Security.CurrentSalesLogixUser;

                string tempPath = "C:\\temp\\Reports\\";
                string report = reporting.GenerateReport(
                    "Provider=SLXOLEDB.1ersist Security Info=True;Initial Catalog=mydbname;Data Source=SLXDEV;User ID=adminassword=\"password\";Extended Properties=\"PORT=1706;LOG=ON;CASEINSENSITIVEFIND=ON;AUTOINCBATCHSIZE=1;SVRCERT=12345;ACTIVITYSECURITY=OFF;TIMEZONE=NONE\"",
                    datasvc.Server,
                    DatabaseServer.dsMSSQL,
                    tempPath,
                    false,
                    false,
                    "OPPORTUNITY.OPPORTUNITYID",
                    user.UserPassword,
                    pluginid,
                    "", 
                    "",
                    "",
                    "SELECT OPPORTUNITY.OPPORTUNITYID FROM OPPORTUNITY",
                    "",
                    user.Id.ToString(),
                    user.UserName);

                ReportDocument doc = new ReportDocument();
                report = string.Format("{0}run\\{1}", tempPath, report);
                doc.Load(report);

	}

I have tried everything I could think of.  Any ideas on what to try next?  I've been beating this up for 2 days.  lease share any ideas.

What happens when you try to open the report (in Crystal Reports Professional) from C:\Temp\Reports? Any more telling errors? Sometimes the error provided through the viewer can be misleading I have found.

I havent had to call Crystal Reports programmatically but I would have thought the connection string would be overridden by the username and password passed to it for security reasons. Have you checked these are coming out correctly (by debugging the above method)?

Thanks,

Nick

You did write the report using the SLX provider didnt you? I.e. didnt "sysdba." all your tables....

The report in C:/temp/Reports works fine when ran as-is.  So the report is fine.  In fact, it is a standard report.  I haven't even gotten to my custom report yet.  I can run the same report from the Reports area in the web client.  But when executed this way, it gets the "logon failed" error.  

Any other ideas on how to control a Crystal report programmatically from within SLX Web?  I have to be able to programmatically export the resulting PDF and email it.  So just using the javascript API to display it doesn't get me where I need to automate the saving/emailing.

I would rule out it being the username and password being passed to the report (as opposed to the connection string). Try it with a user with no password, also try hardcoding the userid and password in the method call.

If you get the report working, with that path, you can then use the Crystal libraries to export the report (then the .NET mail classes to the send the email).

Are you running the code logged in as admin?

I sent your post to a developer who suggested, "Looks like they just need to call doc.SetDatabaseLogon(user, pwd) before loading the report."

Thank you.  The SetDatabaseLogon(...) call worked.  One change though, you have to call it after the doc.Load(report) call otherwise you get an exception.

I'm not exactly sure why you pass in a username and password with the call along with a connection string that has the username and password embedded and then still have to make this call to set the logon params.  But oh well.  Thanks for the help.