Crystal reports 2011 with command object on 64bit for paramters - sql-server-2008

We are using Crystal reports 2011 with SQL Server 2008 R2. We are trying to use dynamic parameters and using command object to populate the dynamic pick list.
The dynamic picklist is not populating and showing just a empty textbox while running on 64bit. I tried to run the profiler and there is no db command executed.
If I use a view instead of command object for populating the parameter - then it works. If I set the IIS to have 'Enable 32 bit application' to true, then even the command object works works. Is this a problem with choosing the correct driver? If so how do I do that?
Any ideas/help?
Thanks
Shankar.

This seems to be a bug in the crystal reports 2011 version.
More details:
http://scn.sap.com/message/14117796
http://scn.sap.com/thread/3342435?start=30&tstart=0
Thanks
Shankar.

Related

#Error in report field when pushing SSRS (.rdl) in PowerBi report server

So, my problem is the following :
I set up a report (.rdl) using Microsoft Report Builder.
In that report, I use a MySQL datasource (I'm connecting to it using ODBC connection string).
In my table i have the following data types :
varchar
text
mediumblob (base64 images stored in DB)
When i run the report locally, everything's working as expected, but when i push the report in Report Server or if i connect to the report server in Report Builder, the images are not showing anymore (blank field and the text datatype field show #Error.
I've spend some time now trying my luck by using visual Studio, modifying a ton of settings in the field expression and other things that i don't remember....
If anyone have an hint, i would be grateful

Use Variable in SQL Command SSIS of ADO net source

I am using Visual Studio 2019 Community edition. I was trying to configure and ADO Net Source using SQL Command. However, I need to pass parameters to it. Is there an easy way to inject SSIS Variables into it?
Yes, you can do it, using expression.
Open data flow task, right-click on empty space there and choose "Properties".
In "Properties" window choose "Expressions"
In opened window choose [Your data source].[SqlCommand] and add you variable there in Expression input.

What is the best method for being able to design a report using SQL 2016?

When I am trying to edit a report by clicking on the design option, an error message is displayed as:
The report builder is not available. Please check the report builder URL in report setup.
So is there anything new with reports in SQL 2016 or am I missing something.
I am using SQL Server standard edition - 13.0.15700.28
Himanshu,
SQL Server 2016 stopped this feature. till SQL server 2014 this functionality working name as clickOne Technology.Error"The report builder is not available. Please check the report builder URL in report setup." is the custom error of your code not a part of SQLServer 2016.
So find any other way to open SSRS reports in design view with report builder.
Use Below mentioned URL.Maybe it helps you to open Reportbuilder URL in SQl Server 2016.with the help of WebBrowser in C#. now we can open Reports builder Successfully.
URL With Html encoding :-"reportbuilder:Action=Edit&ItemPath=%2FProject%2FReports%2FRealization&Endpoint=http%3A%2F%2F101.11.11.111%3A80%2FReportServer"
URL without HTML encoding :-
"reportbuilder:Action=Edit&ItemPath=Project/Reports/Realization&Endpoint=http//101.11.11.111/ReportServer"
If report builder not install first we need to install in local machine after that it's working.
Thanks ,
Kapil

ssis oledb source, as400 parameter not found

I'm using ssis 2008 and I'm trying to get data from an as400 database.
I have a Data Flow Task, and inside it, I have an Oledb Source and in there, I have Data access mode to Sql Command, and I have a query:
select *
from table1
where name = ?
Then i click on the Parameters button and set "name1" for the name of my parameter.
When i ran the ssis, i got error:
Error: The SQL command requires a parameter named ""00001"", which is
not found in the parameter mapping.
So I changed the parameter name to ""00001"" and the ssis worked fine.
Now, the problem is that this same ssis needed to be ran on another as400 server, and older one, and when it ran it showed error:
Error: The SQL command requires a parameter named "", which is
not found in the parameter mapping.
So, now the other server requires a different parameter name.
Is there another way of doing this process using something different than Oledb Source in order to avoid the problem?
What can I do?
We are using sql 2012 and a as400 system and we use a ODBC source for the as400. For our setup it seems to be working. So try the ODBC.
Well, this seems to be an as400 bug, as seen here : [link]http://social.msdn.microsoft.com/Forums/en-US/sqlintegrationservices/thread/5d6ef4f9-1a67-45d1-8a49-eb08becf1408/
On that thread a user says: "This bug is directly related to IBMDA400 from IBM Client Access Tools. There is a bug with the driver passing a parameter to the AS/400. I have proved this out using a third party driver from HiT Software. Passing 00001 is correct using their drivers."
So as I see, it wont matter the method you use, what's need to be done in order to get it working is to pass the parameter with name that AS400 requires. If the parameter with the correct name is passed then the query will work correctly.

"Report item not linked to a dataset"...but it is

I am getting this error in the expression editor for a chart control.
Category - Fields
Item -
'Fields selection frame' is where I see the error
The chart IS linked to a dataset though and it works too; how else would the chart be populated with meangingful data when I run it? :)
Does anyone know why this occurs?
[pic not supplied due to corp firewall]
Looks like a bug in SSRS i.e. the fact that it works anyway but displays an error in the expression editor
It only works when you remove the filter. Its broke, if you put a filter in you get the erroneous error message and no data in your chart. If you remove the filter you get your chart but of course not filtered the way you want. I'm using 2008.
In case anyone else stumbles upon this I can confirm that this still occurs in SQL Server 2008 SP2 (Microsoft SQL Server Reporting Services Designers Version 10.0.4000.0) and also if the report is opened in Report Builder 3.0 (2008 R2).