Friday, March 30, 2012
Problem with SQL string using MS Access and OleDbConnection (ASP .NET)
SELECT ID, LastName + ', ' + FirstName AS Names FROM AgentNames;
Is there any other ways to return a combination like this using an OleDbCommand?
Thanks,
GrierOriginally posted by grier_allen
The string concatination below works in the Query builder built-in to MS Access, but when I try it as an OleDbCommand it doesn't work.
SELECT ID, LastName + ', ' + FirstName AS Names FROM AgentNames;
Is there any other ways to return a combination like this using an OleDbCommand?
Thanks,
Grier
Shot in the dark here but try [LastName + ',' + FirstName] as Names. If not, I dont know why that won't work.
Friday, March 9, 2012
Problem with ReportBuilder
I have this problem:
When I try to access to report builder in HTTP:
http://dwh.site.local/ReportServer/ReportBuilder/reportbuilder.application
all work fine.
When I try to access in HTTPS:
https://dwh.site.local/ReportServer/ReportBuilder/reportbuilder.application
In some client I have this error:
PLATFORM VERSION INFO
Windows : 5.1.2600.131072 (Win32NT)
Common Language Runtime : 2.0.50727.832
System.Deployment.dll : 2.0.50727.832 (QFE.050727-8300)
mscorwks.dll : 2.0.50727.832 (QFE.050727-8300)
dfdll.dll : 2.0.50727.42 (RTM.050727-4200)
dfshim.dll : 2.0.50727.42 (RTM.050727-4200)
SOURCES
Deployment url : https://dwh.site.local/ReportServer/ReportBuilder/reportbuilder.application
ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed
later in the log.
* Activation of https://dwh.site.local/ReportServer/ReportBuilder/reportbuilder.application
resulted in exception. Following failure messages were detected:
+ Downloading https://dwh.site.local/ReportServer/ReportBuilder/reportbuilder.application
did not succeed.
+ The underlying connection was closed: Could not establish trust
relationship for the SSL/TLS secure channel.
+ The remote certificate is invalid according to the validation
procedure.
I have added this configuration in machine.config and web.config of
reportserver/reportmanager:
<system.net>
<settings>
<servicePointManager checkCertificateName="false"
checkCertificateRevocationList="false" />
</settings>
</system.net>
without success...
Help me... pleaseeeeeeeeeeee!
Bye!On Nov 16, 10:29 am, "public int N0UXXZ(){return 0};"
<nous...@.gmail.com> wrote:
> Hi,
> I have this problem:
> When I try to access to report builder in HTTP:http://dwh.site.local/ReportServer/ReportBuilder/reportbuilder.applic...
> all work fine.
> When I try to access in HTTPS:https://dwh.site.local/ReportServer/ReportBuilder/reportbuilder.appli...
> In some client I have this error:
> PLATFORM VERSION INFO
> Windows : 5.1.2600.131072 (Win32NT)
> Common Language Runtime : 2.0.50727.832
> System.Deployment.dll : 2.0.50727.832 (QFE.050727-8300)
> mscorwks.dll : 2.0.50727.832 (QFE.050727-8300)
> dfdll.dll : 2.0.50727.42 (RTM.050727-4200)
> dfshim.dll : 2.0.50727.42 (RTM.050727-4200)
> SOURCES
> Deployment url :https://dwh.site.local/ReportServer/ReportBuilder/reportbuilder.appli...
> ERROR SUMMARY
> Below is a summary of the errors, details of these errors are listed
> later in the log.
> * Activation ofhttps://dwh.site.local/ReportServer/ReportBuilder/reportbuilder.appli...
> resulted in exception. Following failure messages were detected:
> + Downloadinghttps://dwh.site.local/ReportServer/ReportBuilder/reportbuilder.appli...
> did not succeed.
> + The underlying connection was closed: Could not establish trust
> relationship for the SSL/TLS secure channel.
> + The remote certificate is invalid according to the validation
> procedure.
> I have added this configuration in machine.config and web.config of
> reportserver/reportmanager:
> <system.net>
> <settings>
> <servicePointManager checkCertificateName="false"
> checkCertificateRevocationList="false" />
> </settings>
> </system.net>
> without success...
> Help me... pleaseeeeeeeeeeee!
> Bye!
This might help.
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=820552&SiteID=1
Regards,
Enrique Martinez
Sr. Software Consultant|||On 18 Nov, 01:38, EMartinez <emartinez...@.gmail.com> wrote:
> On Nov 16, 10:29 am, "public int N0UXXZ(){return 0};"
[...]
> This might help.http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=820552&SiteID=1
> Enrique Martinez
thank you very much! problem solved.|||On Nov 19, 11:51 am, "public int N0UXXZ(){return 0};"
<nous...@.gmail.com> wrote:
> On 18 Nov, 01:38, EMartinez <emartinez...@.gmail.com> wrote:
> > On Nov 16, 10:29 am, "public int N0UXXZ(){return 0};"
> [...]
> > This might help.http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=820552&SiteID=1
> > Enrique Martinez
> thank you very much! problem solved.
You're welcome. Let me know if I can be of further assistance.
Regards,
Enrique Martinez
Sr. Software Consultant|||The information in that linked post is a little to vague for some of us who
are not up-to-date on the server side of life. Can anyone elaborate? I am
running into the same problem when I try to run Report Builder from one of
our internal web servers.
Thanks!
"EMartinez" wrote:
> On Nov 19, 11:51 am, "public int N0UXXZ(){return 0};"
> <nous...@.gmail.com> wrote:
> > On 18 Nov, 01:38, EMartinez <emartinez...@.gmail.com> wrote:
> >
> > > On Nov 16, 10:29 am, "public int N0UXXZ(){return 0};"
> > [...]
> > > This might help.http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=820552&SiteID=1
> > > Enrique Martinez
> >
> > thank you very much! problem solved.
>
> You're welcome. Let me know if I can be of further assistance.
> Regards,
> Enrique Martinez
> Sr. Software Consultant
>|||On 19 Nov, 23:40, sjauld <sja...@.discussions.microsoft.com> wrote:
> The information in that linked post is a little to vague for some of us who
> are not up-to-date on the server side of life. Can anyone elaborate? I am
> running into the same problem when I try to run Report Builder from one of
> our internal web servers.
> Thanks!
>
> "EMartinez" wrote:
> > On Nov 19, 11:51 am, "public int N0UXXZ(){return 0};"
> > <nous...@.gmail.com> wrote:
> > > On 18 Nov, 01:38, EMartinez <emartinez...@.gmail.com> wrote:
> > > > On Nov 16, 10:29 am, "public int N0UXXZ(){return 0};"
> > > [...]
> > > > This might help.http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=820552&SiteID=1
> > > > Enrique Martinez
> > > thank you very much! problem solved.
> > You're welcome. Let me know if I can be of further assistance.
> > Regards,
> > Enrique Martinez
> > Sr. Software Consultant- Nascondi testo tra virgolette -
> - Mostra testo tra virgolette -
Report Builder in HTTPS check the entire certificate tree.
If client not have the root certificate installed, Report Builder not
start.
If in IIS you have the certificate SSL that is not the root CERT, in
the web client Report Builder not start.
Problem with Report Builder reporting from a remote database
I had the same problem with an earlier build of SQL Server.
The data for my report model is located on a different server than SQL Server 2005. On the SQL Server 2005 server I can use the Report Builder and it works just fine.
When I try to run the Report Builder on my desktop I get the following error:
For more information about this error navigate to the report server on the local server machine, or enable remote errors
-
Cannot create a connection to data source 'dataSource1'.
-
An error has occurred during report processing.
What needs to be in order for users to build reports whose data is located on a different server than SQL Server 2005?
Thanks for your help,
RoyMy guess is you are using Windows Integrated Authentication for connection to both the model and its data source. This won't work if you have two "hops". The typical practice is to store credentials for a user with read-only access to the database on the datasource, and use integrated authentication on the model.
Wednesday, March 7, 2012
Problem with regenerated report model.
Hi,
I regenerated a report model (just added a new field) and now the existing reports created using Report Builder no longer run. I get the following error:
An error has occurred during report processing.
Semantic query compilation failed: e EmptySemanticQuery The SemanticQuery does not contain any Groupings or MeasureGroups. SemanticQuery must contain at least one of these elements. (SemanticQuery '').
When I try to open the report in Repoprt Builder, it does not see any of the entities in the model. Instead, it displays "Unknown Entity".
How can I get the reports to be usable again?
Thanks,
Rocco M.
Hi Rocco,
I am also facing the same issue. Did you find the resolution ?
Thanks
Ashutosh
|||It sounds like you used the Regenerate Model button in Report Manager, which will delete elements of the model if the underlying schema element is no longer present. The Generate command in a VS Report Model project does not do this -- it is only additive.
It appears model regeneration was unable to discover any tables/columns in the underlying database. I don't know why this might have been the case (messed up connection string?), but unfortunately the model is gone now, and it will be very tedious to resuscitate your reports. If you have a recent backup of your report server database, you are in much better shape, however.
Server-based model generation is for quick-and-dirty scenarios. If you are serious about developing and deploying reports based on a report model, you should create one in Visual Studio (or create an empty project, download the generated one from the server, and add it to the project). You will have much finer control over the evolution of the model over time, and it will be much easier to maintain backups and/or old versions as needed.
|||
Hi Ashutosh,
I did not find a resolution to this problem. All of the reports created with Report Builder needed to be re-created. This was not a good situation.
All of the changes made to the report model were done using Visual Studio.
To prevent this situation from happening again, I have created a duplicate "development" version of the report model. All proposed changes are first done to this development version and some reports created specifically against this development version are used to verify proper operation. If the verification is successful, the changs are then made to the production version of the report model using the exact same steps performed on the development version.
Regards,
Rocco
Problem with regenerated report model.
Hi,
I regenerated a report model (just added a new field) and now the existing reports created using Report Builder no longer run. I get the following error:
An error has occurred during report processing.
Semantic query compilation failed: e EmptySemanticQuery The SemanticQuery does not contain any Groupings or MeasureGroups. SemanticQuery must contain at least one of these elements. (SemanticQuery '').
When I try to open the report in Repoprt Builder, it does not see any of the entities in the model. Instead, it displays "Unknown Entity".
How can I get the reports to be usable again?
Thanks,
Rocco M.
Hi Rocco,
I am also facing the same issue. Did you find the resolution ?
Thanks
Ashutosh
|||It sounds like you used the Regenerate Model button in Report Manager, which will delete elements of the model if the underlying schema element is no longer present. The Generate command in a VS Report Model project does not do this -- it is only additive.
It appears model regeneration was unable to discover any tables/columns in the underlying database. I don't know why this might have been the case (messed up connection string?), but unfortunately the model is gone now, and it will be very tedious to resuscitate your reports. If you have a recent backup of your report server database, you are in much better shape, however.
Server-based model generation is for quick-and-dirty scenarios. If you are serious about developing and deploying reports based on a report model, you should create one in Visual Studio (or create an empty project, download the generated one from the server, and add it to the project). You will have much finer control over the evolution of the model over time, and it will be much easier to maintain backups and/or old versions as needed.
|||
Hi Ashutosh,
I did not find a resolution to this problem. All of the reports created with Report Builder needed to be re-created. This was not a good situation.
All of the changes made to the report model were done using Visual Studio.
To prevent this situation from happening again, I have created a duplicate "development" version of the report model. All proposed changes are first done to this development version and some reports created specifically against this development version are used to verify proper operation. If the verification is successful, the changs are then made to the production version of the report model using the exact same steps performed on the development version.
Regards,
Rocco