Showing posts with label accessing. Show all posts
Showing posts with label accessing. Show all posts

Sunday, March 11, 2012

Re: Accessing the underlying sql query from the rdl file

Our client uses the report builder to generate reports for collection of employees. We would like to use the employee records in this report to perform some additional processing (such as the list of employees gets assigned to a particular group).

Programmatically, I can retrieve a byte stream from rs.GetReportDefinition( "\myClientEmpReport") and deserialize the stream into Report object (as define by ReportDefinition.xsd).

I can then manually drill down and retrieve the SematicQuery xml from the commandText field.

The problem is how to convert the SemanticQuery format into a T-Sql query that I can run against the view that the report model is based off of.

Is this possible?

Thanks,

Arjay

P.S. Running SQL 2005 Reporting Services, VC# 2005, ASP.Net 2.0.

After attempting to autogenerate serialization classes on the SemanticQuery xml with Xsd and XsdObjectGen, I ended up hand coding some classes that handled recursion. From there, I was able to regenerate the sql query by walking through the filter and grouping sections. While this isn't a generic solution, it works well for my needs because the model I need this for is a single datasource derived from a view.

As a feature request, it sure would be nice to be able get the query string from the reporting engine directly.

Sunday, February 19, 2012

[DBNETLIB][ConnectionWrite (send()).] errors

We have a Dell 2950 running Windows 2003 connecting to SQL2005 Database.

Users accessing their SQL application are getting this error message after leaving the application open for a period when they are not accessing the system. We have run the application on two different servers and cannot re-create the errors, which might suggest a hardware problem with our server, but as yet we haven't identified the problem.

Does anyone have any ideas ?

Hi Brian,

I'm having similar issues with my system (new HP server running Win 2003 & SQL 2005 with VB App running on XP Clients, MDAC 2.81). Seems to affect certain PC's, doesn't affect a version of the VB 6 App running locally on the server, or one of the Clients that continually polls the server once per minute, 24/7.

The error handling in the VB App actually writes a log of the error to a SQL Table, which suggests that the connection error occurs, and by the time the user confirms the msgbox prompt the connection comes back up, allowing the log to be written...

I've tried disabling connection pooling in the ADO connection string & the SynAttackProtect REG setting change as discussed at http://www.eggheadcafe.com/ng/microsoft.public.sqlserver.connect/post22689813.asp

Both to no avail....

Was wondering if you'd found a resolution yet?

Best regards

Keith
|||

For your issue, I would try to follow the article http://support.microsoft.com/default.aspx?scid=kb;en-us;899599 to add the registry key. Maybe that will fix your problem. If not, please provide more information on the infrastructure to help us narrow the issue.

HTH

|||umm - our problem appeared to hardware - Dell announced urgent driver updates for the cards in our server, but that didn't entirley solve the problem although it is better. The the support desk for hte application we are using then recomended switching the server to use both TCP/IP and Named Pipes and then adjusting the client config appropriatly. this seems to have resolved our issue

[DBNETLIB][ConnectionWrite (send()).] errors

We have a Dell 2950 running Windows 2003 connecting to SQL2005 Database.

Users accessing their SQL application are getting this error message after leaving the application open for a period when they are not accessing the system. We have run the application on two different servers and cannot re-create the errors, which might suggest a hardware problem with our server, but as yet we haven't identified the problem.

Does anyone have any ideas ?

Hi Brian,

I'm having similar issues with my system (new HP server running Win 2003 & SQL 2005 with VB App running on XP Clients, MDAC 2.81). Seems to affect certain PC's, doesn't affect a version of the VB 6 App running locally on the server, or one of the Clients that continually polls the server once per minute, 24/7.

The error handling in the VB App actually writes a log of the error to a SQL Table, which suggests that the connection error occurs, and by the time the user confirms the msgbox prompt the connection comes back up, allowing the log to be written...

I've tried disabling connection pooling in the ADO connection string & the SynAttackProtect REG setting change as discussed at http://www.eggheadcafe.com/ng/microsoft.public.sqlserver.connect/post22689813.asp

Both to no avail....

Was wondering if you'd found a resolution yet?

Best regards

Keith
|||

For your issue, I would try to follow the article http://support.microsoft.com/default.aspx?scid=kb;en-us;899599 to add the registry key. Maybe that will fix your problem. If not, please provide more information on the infrastructure to help us narrow the issue.

HTH

|||umm - our problem appeared to hardware - Dell announced urgent driver updates for the cards in our server, but that didn't entirley solve the problem although it is better. The the support desk for hte application we are using then recomended switching the server to use both TCP/IP and Named Pipes and then adjusting the client config appropriatly. this seems to have resolved our issue

Monday, February 13, 2012

[?] Error accessing from internet

I've installed Reporting Services and customized the authentication ( Forms
Authentication Sample ) with SSL.
Everything works fine in intranet environment.
Now I'm trying to publish this server in internet, but it doesn't work:
when I call the server url I can see the login form, but when I press the
"Login" button nothing happens.
I debugged the application and see the request coming in correctly, the
login credentials are authenticated but the redirect to the
"/Pages/Folder.aspx" is wrong.
It seems like the report manager and the report server can't communicate
each other when accessed from internet.
May the SSL certificate be released on Netbios name but the internet access
is something like www.myserver.com ?
Thanks for responses.
MorenoI had a similar problem. What I did was add a entry into my host file
on the server. Make sure your internal ip for the server matches your
domain name. Hope this helps.
Example:
10.0.0.1 yourssldomain.com
"Moreno" <movendra@.yahoo.com> wrote in message news:<#Q$tpBtWEHA.3800@.TK2MSFTNGP11.phx.gbl>...
> I've installed Reporting Services and customized the authentication ( Forms
> Authentication Sample ) with SSL.
> Everything works fine in intranet environment.
> Now I'm trying to publish this server in internet, but it doesn't work:
> when I call the server url I can see the login form, but when I press the
> "Login" button nothing happens.
> I debugged the application and see the request coming in correctly, the
> login credentials are authenticated but the redirect to the
> "/Pages/Folder.aspx" is wrong.
> It seems like the report manager and the report server can't communicate
> each other when accessed from internet.
> May the SSL certificate be released on Netbios name but the internet access
> is something like www.myserver.com ?
> Thanks for responses.
> Moreno