Showing posts with label java. Show all posts
Showing posts with label java. Show all posts

Monday, March 26, 2012

MSRS Java Client

We tried to develop a MSRS Java Client to communicate with the MSRS server
via web services. Because of integrated windows authentication, we
encountered an access denial error. Has anyone encountered this problem and
know how to embed windows security in the Java client. By the way, I used
Apache Axis to create client stub classes from a WSDL file. I obtained the
WSDL file from the MSRS server directly.
Thanks,
JamesJames, I am trying to do exactly what you are describing and have run into
the same problem. Did you ever discover a solution?
Thanks!
"James" wrote:
> We tried to develop a MSRS Java Client to communicate with the MSRS server
> via web services. Because of integrated windows authentication, we
> encountered an access denial error. Has anyone encountered this problem and
> know how to embed windows security in the Java client. By the way, I used
> Apache Axis to create client stub classes from a WSDL file. I obtained the
> WSDL file from the MSRS server directly.
> Thanks,
> James|||Josh, James, I'm having this problem as well. Was there a solution?
"Josh Hensley" wrote:
> James, I am trying to do exactly what you are describing and have run into
> the same problem. Did you ever discover a solution?
> Thanks!
> "James" wrote:
> > We tried to develop a MSRS Java Client to communicate with the MSRS server
> > via web services. Because of integrated windows authentication, we
> > encountered an access denial error. Has anyone encountered this problem and
> > know how to embed windows security in the Java client. By the way, I used
> > Apache Axis to create client stub classes from a WSDL file. I obtained the
> > WSDL file from the MSRS server directly.
> >
> > Thanks,
> >
> > James|||Hey LT,
I did find a solution, but forgot to come back and mention it here.
The problem comes from the fact that we need to call the Render method
without specifying some optional parameters (like historyID). When you call
a Web Service API method from Java and leave out an optional parameter, the
SOAP message that is generated by AXIS can either exclude the tag for that
missing parameter or include the tag with a special attribute saying it's not
being used (xsi:nil="true"). The default for behavior for AXIS is to send
the tag with the special attribute but apparently Microsoft Reporting
Services doesn't want the tag sent at all. So you have to modify AXIS to
satisfy Reporting Services and stop sending tags for arguments that aren't
specified.
A much more detailed explanation is in this article written by a fella from
France. (You will have to register on their site to read the article)
http://www.sqlreportingservices.net/Tools/1996.aspx
Good luck!
"LT" wrote:
> Josh, James, I'm having this problem as well. Was there a solution?
> "Josh Hensley" wrote:
> > James, I am trying to do exactly what you are describing and have run into
> > the same problem. Did you ever discover a solution?
> >
> > Thanks!
> >
> > "James" wrote:
> >
> > > We tried to develop a MSRS Java Client to communicate with the MSRS server
> > > via web services. Because of integrated windows authentication, we
> > > encountered an access denial error. Has anyone encountered this problem and
> > > know how to embed windows security in the Java client. By the way, I used
> > > Apache Axis to create client stub classes from a WSDL file. I obtained the
> > > WSDL file from the MSRS server directly.
> > >
> > > Thanks,
> > >
> > > Jamessql

Friday, March 23, 2012

msmq missing messages after applying SP3a to SQL server

Used to work fine:
(windows 200 server, sql server 2000, JDBC driver SP2.)
Two java processes, one sending messages (using jdbc and sql as temp storage), second is receiving and placing on msmq.

After installing SP3a for SQL server, under high load (200 a sec) there are missing messages in msmq.
Installed everything from scratch on separate machine, works fine until SP3a is applied.
Any help is highly appreciatedCheck for error messages on the box with SP3. M$ closed the hole for buffer overflow. JDBC by default is declaring @.Px as NVARCHAR(4000). If you are not handling TYPEing correctly, post-SP3 machine will post something like "Invalid TDS packet sent by client" error to the log.|||That would be where I look first. With sp3/3a microsoft modified quite a bit on the security side which has caused problems in other areas as well. Check your event logs and sql server logs. If nothing there, use sql profiler on the test machine and trap on "errors and warnings".|||actually, i belive it was a good thing they addressed this, but a bad thing the way they did it. now the bewildered and confused jdbc coders are looking out the window and wondering if the world's really ending or it's just their code...