11/28/2024 7:26:50 PM
|
| |
| slxdeveloper.com Community Forums |
|
| |
|
|
The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
Forum to discuss reports for SalesLogix including Crystal, SQL Reports, etc. View the code of conduct for posting guidelines.
|
|
|
|
Web Reporting not working in a 64 bit Environment...Any ideas?
Posted: 13 Mar 09 7:57 AM
|
Client System Information:
Sage SalesLogix Version: 7.5.1.1742
Crystal Report Version: XIR2 (with SP3)
Operating System: Windows Server 2003 Standard x64 Edition
DOT Framework Installed: 3.5 (with SP1)
We have one of our client (with the above system information) where we have implemented Sage SalesLogix V7.5 Web Client (with Web Reporting). Whenever we are running any parameterized reports we are getting an error stating that...
Method Not found: 'Void CrystalDecisions.ReportAppServer.ReportDefModel.ISCrPromptingRequestInfo.set_RequestOptions (CrystalDecisions.ReportAppServer.DataDefModel.PropertyBag)'.
Here one thing we would like to mention that any reports which are not parameterized (i.e. accepts no parameter) runs without any issues.
Can you guys shed some light in this regard?
Your reply is much appreciated!
Sincerely,
Dinesh |
|
|
|
Re: Web Reporting not working in a 64 bit Environment...Any ideas?
Posted: 14 Mar 09 4:31 PM
|
I don't know the answer. But first, check the report for the parameters it is expecting. I've found that using the built in SalesLogix "filters" (from the Reports screen) has odd affects on the use of the parameters you build into the actual report. Also check for the latest service packs for SQL Server. And there is also a newer version of the 64 bit operating system: Windows 2008.
Best of luck. |
|
|
|
Re: Web Reporting not working in a 64 bit Environment...Any ideas?
Posted: 16 Mar 09 10:07 AM
|
Hi Robert,
SQL 2005 SP3 is installed, still no luck.
As for the error, it seems that, the problem is with the UI compenent (which displays the parameters for the Crystal reports). Its throwing an error when the UI compenent is getting loaded whenever any User is running the parameterized reports.
Any more ideas?
Sincerely,
Dinesh |
|
|
|
Re: Web Reporting not working in a 64 bit Environment...Any ideas?
Posted: 17 Mar 09 10:01 AM
|
Again, I'm not sure what the answer is, but in a past 64 bit installation we had an error based on a few of the components being installed. The answer in our case, was to find an operating system option setting that permitted the use of 32 bit modules in the 64 bit environment. I'm not sure where in Computer Management to find that option again, and I'm not sitting in front of a 64 bit machine. Try to find that option, set it for 32 bit compliance and try testing again.
|
|
|
|
Re: Web Reporting not working in a 64 bit Environment...Any ideas?
Posted: 17 Mar 09 1:15 PM
|
A couple of items to check/try
Have you verified the Web Site is in IIS6 compatability mode?
Are the Application pools set to Classic? (this enables 32 bit)
Is ASP 32 bit enabled?
You may want to google the Business Objects site as well.
Carla |
|
|
|
Re: Web Reporting not working in a 64 bit Environment...Any ideas?
Posted: 07 Apr 09 4:14 AM
|
I have the same problems. But my environment is a Windows 2003 Ent Server R2 SP2 in Italian.
However I have the SQL Server 64 2005 SP2 installed on another machine.
I have no problems with reports without parameters, but with parameters I get the same identical error.
I am using a SalesLogix 7.5.1 Web Client, with the new Web Reporting.
Of course I try to reinstall more times [Crystal Server XI R2 with SP3], but no luck.
How could I fix this?
Thank you,
bye!
 |
|
|
|
Re: Web Reporting not working in a 64 bit Environment...Any ideas?
Posted: 05 May 09 2:14 AM
|
Hi All,
We were able to resolve this particular issue. The steps that we took to solve it are as follows:
1. The web reporting does not work on a 64 bit environment. Hence, we changed the environment from 64 bit to 32 bit.
2. As both the servers (Web Host server and Web Reporting server) were on different workgroups, As the request process took a lot of time, we first increased the connection timeout of the website, tab. But that too didn't solve the issue.
3. Then, under the ASP.NET tab of the website properties, we changed the configuration and from the configuration settings, we increased the value of "Request Execution timeout (seconds)" under the application tab.
Bingo!!, the reports started working fine. 
Cheers,
Dinesh |
|
|
|
Re: Web Reporting not working in a 64 bit Environment...Any ideas?
Posted: 05 May 09 4:25 AM
|
Hi Dinesh,
I try to increase the values as you suggest [I put 310 seconds in both SLX Web Reporting site and SalesLogix Site] on ASP.NET -> tab Application -> Request Execution timeout, and also I try to change too the timeout of the sites, but I got no luck.
The error still remain the same, and consider I try to to a full 32bit environment [SLX Server,SQL server, Crystal Server...]
Are you sure you just touch this??? could you tell me the exact values you put on every site?
|
|
|
|
Re: Web Reporting not working in a 64 bit Environment...Any ideas?
Posted: 05 May 09 5:39 AM
|
Hi Valter,
From your earlier posts, it looks like your SalesLogix and SLX Web Reporting Sites are on the same server (i.e. Web Host and Web Reporting installed are on the same server).
Operating System: Windows 2003 Enterprise Server R2 SP2 (32 bit)
Sage SalesLogix Version: 7.5.1.1742
Crystal Report Version: XIR2 (with SP3)
Database Server is 64 bit.
Please confirm…
In our case, we also received the same error. Hence we performed certain steps on the Web Reporting Server (Web reporting installed on different server and not in the same workgroup as of Web Host Server)…
1. We did complete reinstallation i.e. first uninstalled…
a. We uninstalled the Crystal Report Server and Service pack 3 for the same.
b. We uninstalled the Web Reporting.
c. We uninstalled the Application Architect (this was installed on the Web Reporting as we needed to deploy the Web Reporting on the Web Reporting Server)
2. After that, we installed…
a. We installed the Crystal Report Server and then the Service pack 3 for the same.
b. We installed Web Reporting and Application Architect.
c. We installed the Service Pack 1 for Web Reporting and Application Architect.
3. After doing the above, we logged in to Application Architect (i.e. connected to the Web Host Server) and then deployed the Web Reporting on the Web Reporting Server.
4. This resolved the above mentioned error (that you are getting).
After that, when we were not able to see the reports because of the requst timeout error (as both these servers are not in the same domain), we increased the timeout for the SLX Web Reporting site. Still no luck?. Then we changed the value of “Request Execution timeout (seconds)” field (i.e. under ASP.NET tab -> Edit Configuration -> Application tab) to 540. After making this change, the Web Reporting was running just fine for parameterized as well as for Non-Parameterized.
HTH.
Have a great day!
Sincerely,
Dinesh
|
|
|
|
Re: Web Reporting not working in a 64 bit Environment...Any ideas?
Posted: 05 May 09 11:26 AM
|
Hi,
I confirm my configuration, and I also tried to another machine completely 32bit also with SQL Server 2005 32bit.
I had no luck also putting 540 as execution timeout of ASP.NET, I still got the same error,and I installed Crytal on the same server, I confirm.
So I have no idea how solve, and I'm not sure your suggestion could solve my problem.
Anyone of this forum has succesfully installed 7.5.1 with Crystal Server and Reports with parameters working?
Thanks,
bye!
|
|
|
|
Re: Web Reporting not working in a 64 bit Environment...Any ideas?
Posted: 08 May 09 12:09 PM
|
I've been fighting this exact same issue for three weeks now and Sage hasn't been able to assist - hopefully you guys can.
Environment:
Web Reporting Server: Windows Server 2003 32 bit
App / Web Server: Tried both Server 2008 32 bit and Server 2003 32 bit (current OS)
SQL Server: 2005 64 bit
All web reports are perfect except for parameterized reports. They always result with:
"Method not found: 'Void CrystalDecisions.ReportAppServer.ReportDefModel.ISCRPromptingRequestInfo.set_RequestOptions(CrystalDecisions.ReportAppServer.DataDefModel.PropertyBag)'."
I quadrupled the timeout, and that solved nothing.
I uninstalled SalesLogix Web Reporting and Crystal and reinstalled them to the C drive (were on D) that solved nothing.
I've manually (as opposed to automatically) created the web reporting website in IIS, that solved nothing.
We've changed the App server from 2008 to 2003, that solved nothing.
One thing I did notice is that after the first installation of Web Reporting I could never reinstall it and have it create the website. It would always fail or get 'interrupted'. (I tried this from both the CD and the downloaded .iso from the FTP site - same results.)
Also another odd thing: Upon installing both Web Reporting AND SP1 for 7.5 on the web reporting box I'd get an 'Assembly Not Found' message box near the end (no matter the installation source - DVD or downloaded .iso) - Crystal always installed just fine, though.
Any thoughts, suggestions, etc to get this thing functional?
|
|
|
|
Re: Web Reporting not working in a 64 bit Environment...Any ideas?
Posted: 13 May 09 1:16 PM
|
RESOLVED! Oh glorious day!
This problem is isolated to the Web Reporting server, so ignore the other pieces to the SalesLogix puzzle.
This occurs when the Crystal installation puts the 1.1 framework .dll into the GAC because it didn't 'sense' that 2.0 was there. (Personally I think Crystal needs to update this check.)
You can validate this by going to \windows\assembly and looking at the properties of 'CrystalDecisions.ReportAppServer.ReportDefModel'. The version *should be* 11.5.9509.1202. (This is the correct 2.0 framework .dll)
If you see version 11.5.9503.550 then you have the 1.1 framework .dll in the GAC and this is your problem.
I'm not sure if simply dragging the correct .dll from \program files\Business Objects\Common\3.5\managed\dotnet2 into windows\assembly will actually work or not. (I wasn't brave enough to try - theory is it should. Check the version both before and after, of course.)
Well Byrnes, that sounds great, but how do I absolutely make certain that Crystal detects the 2.0 framework and installs the correct .dll to start with?
I'm glad you asked.
From a virgin OS state, do the following:
Install IIS (make certain that ASP.NET is checked!)
Do all windows updates, with all frameworks and framework service packs.
Open IIS and look at allowed extensions.
If Asp.NET 2.0 is not listed as an allowed extension then:
From windows\Microsoft.Net\Framework\v2.0.50727 run: aspnet_regiis -i
The extension should now be listed and allowed within IIS
Now you can install Crystal and follow the implementation guide.
My problem was that ASP.NET was installed and an allowed extension, but ASP.NET wasn't checked under the Add/Remove Windows Components where you install IIS from. Which means this list isn't an either/or list. Doesn't work that way. (At least not in Windows Server 2003 - it might behave slightly differently in R2, I'm honestly not sure.) Consider it a finite list where all must be accomplished or this might happen.
Well I've had my fun, where's the bar?
|
|
|
| |
|
Re: Web Reporting not working in a 64 bit Environment...Any ideas?
Posted: 22 May 09 8:30 AM
|
YES, YES, YES!!!! You are BIG 
I just do like this:
I go to the %PROGRAMFILES%\Business Objects\Common\3.5\managed\dotnet2, I select all those files:
CrystalDecisions.ReportAppServer.ClientDoc.dll
CrystalDecisions.ReportAppServer.CommLayer.dll
CrystalDecisions.ReportAppServer.CommonControls.dll
CrystalDecisions.ReportAppServer.CommonObjectModel.dll
CrystalDecisions.ReportAppServer.Controllers.dll
CrystalDecisions.ReportAppServer.CubeDefModel.dll
CrystalDecisions.ReportAppServer.DataDefModel.dll
CrystalDecisions.ReportAppServer.DataSetConversion.dll
CrystalDecisions.ReportAppServer.ObjectFactory.dll
CrystalDecisions.ReportAppServer.ReportDefModel.dll
CrystalDecisions.ReportAppServer.XmlSerialize.dll
I drag And Drop all those files to the folder %WINDIR%\assembly
I do from prompt command iisreset.
That's All!! Everything works!!!
Thank you man, this problem make me crazy.
Bye!
|
|
|
| |
| |
| |
|
You can
subscribe to receive a daily forum digest in your
user profile. View the site code
of conduct for posting guidelines.
 Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!
|
|
|
|
|
|
|
|