I will investigate the Reports form method going forward but our fix turned out to be maddeningly simple: change the report location from Embedded to Local. We only discovered this after a one hour WebEx session with Support. We could reproduce the issue perfectly with the 7.0.1 client, it worked when set to local but running the active link while the report was embedded actually seemed to lock up the Remedy service on the server. A bug is being opened by Remedy Support for this issue (I have already sent them my defs and some data so that they can reproduce it on their end). I can post the bug number later if anyone is interested (once the bug has actually been opened). Luckily all of my users have a common drive letter so that I can go through all my active links that call Crystal reports and change them to Local and I'll be in business, this even worked worked with the 5.1.2 client. I will push my desktop support folks to get the 7.0.1 client installer package finished more quickly in light of the suggestions here to keep the versions in sync. Thanks to everyone who responded, Rick
________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Grooms, Frederick W Sent: Monday, March 03, 2008 1:28 PM To: [email protected] Subject: Re: Crystal 9 embedded reports not working on ARS 7.0.1 ** You can still use the Report form to store your reports. (We found that the embedded was what was causing our problems. Something about how embedded is stored in the db and the AL trying to save it to the local machine to run it having to make multiple calls.) Save your report and Attach it to a new Report Form Record. Change Location on the AL to Report Form and make the Report Name on the AL the same value you put in the Report form (That's the unique tie between the AL and the Report Form). This also has the plus that you can change a Report and not have to have any user log out and back in to get the new version of the report. Fred ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Rick Westbrock Sent: Monday, March 03, 2008 3:04 PM To: [email protected] Subject: Re: Crystal 9 embedded reports not working on ARS 7.0.1 Thanks to Frederick and Susan for your replies. I'm calling the reports using an Open Window action (not a macro), this has been the case for several years. The active link was imported via def file from the 5.1.2 server into the 7.0.1 server. I don't use the Report form for this application, the users click a button on a display form which in turn calls the active link. The only action in the AL is an Open Window as follows: Window Type: Report Target Location: New Server Name: the new 7.0.1 server Form Name: CM:ChangeManagement (the regular form that has the data for the report) Form View: (Clear) The qualification is ( 'Implementation Date/Time' > $TIMESTAMP$) AND ( 'Implementation Date/Time' < ($TIMESTAMP$ + (((60 * 60) * 24) * 10))) AND ( 'Status' = "Approved") The Report Information tab shows this: Report Type: Crystal Name: the correct path & file name appear here Destination: Screen Operation: Run Location: Embedded Query Override: Yes I opened a case with Support and they said that the 5.1.2 user tool is not supported with 7.0.1 server (but we have used on older WUT against a newer server before with no issues and all other functionality works fine). Below are other notes from Support for this case: "This is due to incomparability between arodbc driver and the version that Crystal report application uses. I have seen this problem and re-installing the user tool has helped. Also ensuring that the user DSN is pointed to the right server (Each user must manually configure the Remedy ODBC under User DSN then it will allow the users to access the reports without error) has also resolved this problem. If the problem still exists then open the report in crystal 11 versions and re-save it. I hope this helps because user tool 7.x version is compatible with crystal 11 reports." My laptop which is a fresh install of Windows XP Pro and WUT 7.0.1 patch 6 displays the 1904 error so it's not strictly WUT version related. I actually re-installed over the top and still get the error on this clean laptop (which has never had any version of Crystal tools on it nor any other version of the WUT). The laptop has a user DSN for Remedy as does the server. Of course we don't own any version of Crystal higher than 9 so upgrading it not an option at this time. ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Grooms, Frederick W Sent: Monday, March 03, 2008 12:38 PM To: [email protected] Subject: Re: Crystal 9 embedded reports not working on ARS 7.0.1 We had some problems with Crystal embedded in ALs when we switched from 5.1.2 to 6.3 as well. We saved the reports out of the ALs and imported them as attachments into the Report form (luckily we didn't have that many embedded). We then switched those ALs to use the Window Open (Window Type=Report). In oder to keep compatability (while we migrated users to the new User Tool) we kept the old ALs and just added to their Run-If ($VERSION$ like "%5.01.%"). The new ALs have (NOT ($VERSION$ like "%5.01.%")) in their Run-If. Fred ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Rick Westbrock Sent: Monday, March 03, 2008 2:06 PM To: [email protected] Subject: Crystal 9 embedded reports not working on ARS 7.0.1 Hello all- My current production environment is ARS 5.1.2 patch 1283 (server and WUT) and I have several buttons that call active links to open Crystal reports; these reports were written with version 9 of Crystal Reports Designer. This process has been working fine for several years now. The report files are embedded in the active links. The application and database servers are both Windows 2000 (SQL 2000) and the users are on XP Pro. We are in the process of upgrading to version 7.0.1 patch 6 (installed fresh on a new server running Windows Server 2003 Standard) and I've discovered that the Crystal reports do not work against this server. The new 7.0.1 server is pointing to a new database on the existing DB server. When using WUT 5.1.2 (as my users will be for a time after we repoint to the new server) they get an hourglass for a minute or so and then nothing. When using the 7.0.1 patch 6 WUT the hourglass comes up for 1-2 minutes but then the following error is displayed: An error occurred while generating the Crystal report: 0x80043ac3 - File not found. Details: error (ARERR 1904) The error message catalog doesn't show this error number (1904) and I searched the KB and couldn't my exact problem there, either. I did find solution #214704 but that was regarding the user having another Crystal Reports component on their system (which is not applicable in this case). None of the other six KB results was applicable, either. This morning I had a user open his 5.1.2 WUT and he was able to open a Crystal report against the 5.1.2 server with no issue. I had him log in again, this time to the 7.0.1 server and the report window never opens so I believe that I've narrowed down the issue to the ARS version (or possibly the Windows version of the server). This user has never had a version of the WUT higher than 5.1.2 installed on his machine. When I opened the active link in the 7.0.1 Admin tool the type was set to 2 instead of Crystal so I used the menu to change it to Crystal and saved the AL but that didn't help. I also resaved the .rpt file into the AL and that didn't help either. Has anyone else run into Crystal Reports problems when upgrading to version 7 (any flavor)? Thanks, Rick __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
