jcifs.smb.SmbException: Incorrect function

[harald.preczek]

Hi,

we have an application running on IBM Websphere 5.1/6.1 (hosted on Sun
Solaris 10) using jcifs to access a fileshare on a netapp-filer via smb and
write files into a windows filesystem.

Since the filer was updated to Ontap 7.2.3 we receive "
jcifs.smb.SmbException: Incorrect function".

This looks like a problem that should be fixed with jcifs-1.2.15. We tried
every jcifs-version since then, but it still won't work.

It also didn't change when we moved from Websphere 5.1 to 6.1.

On an older filer with Ontap 7.0.6 it still works.

Netapp refuses to solve the problem since they think their software works
correctly.

I found this link on the web desribing the same problem with jcifs-1.2.17
and forwarded it to the netapp support, but i'm not very hopeful.

http://www.nabble.com/SmbFileOutputStream-with-append%3Dtrue-misbehaving-on-a-certain-NAS-td14944774.html

Here is a part of the stacktrace

jcifs.smb.SmbException: Incorrect function.
      [10.12.07 10:36:07:983 IRST]   d5454d SystemErr     R   at
      jcifs.smb.SmbTransport.checkStatus(SmbTransport.java:583)
      [10.12.07 10:36:07:983 IRST]   d5454d SystemErr     R   at
      jcifs.smb.SmbTransport.send(SmbTransport.java:683)
      [10.12.07 10:36:07:983 IRST]   d5454d SystemErr     R   at
      jcifs.smb.SmbSession.sessionSetup(SmbSession.java:330)
      [10.12.07 10:36:07:983 IRST]   d5454d SystemErr     R   at
      jcifs.smb.SmbSession.send(SmbSession.java:269)
      [10.12.07 10:36:07:984 IRST]   d5454d SystemErr     R   at
      jcifs.smb.SmbTree.treeConnect(SmbTree.java:154)
      [10.12.07 10:36:07:984 IRST]   d5454d SystemErr     R   at
      jcifs.smb.SmbFile.connect(SmbFile.java:806)
      [10.12.07 10:36:07:984 IRST]   d5454d SystemErr     R   at
      jcifs.smb.SmbFile.connect0(SmbFile.java:772)
      [10.12.07 10:36:07:984 IRST]   d5454d SystemErr     R   at
      jcifs.smb.SmbFile.open0(SmbFile.java:837)
      [10.12.07 10:36:07:984 IRST]   d5454d SystemErr     R   at
      jcifs.smb.SmbFile.open(SmbFile.java:866)
      [10.12.07 10:36:07:984 IRST]   d5454d SystemErr     R   at
      jcifs.smb.SmbFileOutputStream.<init>(SmbFileOutputStream.java:142)
      [10.12.07 10:36:07:985 IRST]   d5454d SystemErr     R   at
      jcifs.smb.SmbFileOutputStream.<init>(SmbFileOutputStream.java:97)
      [10.12.07 10:36:07:985 IRST]   d5454d SystemErr     R   at
      jcifs.smb.SmbFileOutputStream.<init>(SmbFileOutputStream.java:67)
      [10.12.07 10:36:07:985 IRST]   d5454d SystemErr     R   at
      jcifs.smb.SmbFile.getOutputStream(SmbFile.java:2625)
      [10.12.07 10:36:07:985 IRST]   d5454d SystemErr     R   at
      de.bundesbank.esb.web.view.RootRiverView.renderToUrl(RootRiverView.java:134)

Does anybody know a solution or a workaround?

Best regards
Harald
_____________________________________________________
Harald Preczek
Deutsche Bundesbank
Zentralbereich IT
Produktmanagement Anwendungssysteme
Wertpapier, Kredit, Devisen, Risiko-Controlling, Depot
Tel: [phone] | Fax: [phone]
Email: harald.preczek@...
Homepage: www.bundesbank.de

(Embedded image moved to file: pic08793.jpg)


--
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail
irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und
vernichten Sie diese E-Mail. Das unerlaubte Kopieren sowie die unbefugte
Weitergabe dieser Mail oder von Teilen dieser Mail ist nicht gestattet.

Wir haben alle verkehrsüblichen Maßnahmen unternommen, um das Risiko der
Verbreitung virenbefallener Software oder E-Mails zu minimieren, dennoch
raten wir Ihnen, Ihre eigenen Virenkontrollen auf alle Anhänge an dieser
Nachricht durchzuführen. Wir schließen außer für den Fall von Vorsatz oder
grober Fahrlässigkeit die Haftung für jeglichen Verlust oder Schäden durch
virenbefallene Software oder E-Mails aus.

Jede von der Bank versendete E-Mail ist sorgfältig erstellt worden, dennoch
schließen wir die rechtliche Verbindlichkeit aus; sie kann nicht zu einer
irgendwie gearteten Verpflichtung zu Lasten der Bank ausgelegt werden.
______________________________________________________________________

This e-mail may contain confidential and/or privileged information. If you
are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail. Any
unauthorised copying, disclosure or distribution of  the material in this
e-mail or of parts hereof is strictly forbidden.

We have taken precautions to minimize the risk of transmitting software
viruses but nevertheless advise you to carry out your own virus checks on
any attachment of this message. We accept no liability for loss or damage
caused by software viruses except in case of gross negligence or willful
behaviour.

Any e-mail messages from the Bank are sent in good faith, but shall not be
binding or construed as constituting any kind of obligation on the part of
the Bank.

[tinius_paul]

Are you accessing the filer using the FQDN name? Just using the hostname fixed it for us.

Paul

-----Original Message-----
From: jcifs-bounces+tinius_paul=emc.com@... [mailto:jcifs-bounces+tinius_paul=emc.com@...] On Behalf Of harald.preczek@...
Sent: Friday, June 06, 2008 5:21 AM
To: jcifs@...
Subject: [jcifs] jcifs.smb.SmbException: Incorrect function



Hi,

we have an application running on IBM Websphere 5.1/6.1 (hosted on Sun Solaris 10) using jcifs to access a fileshare on a netapp-filer via smb and write files into a windows filesystem.

Since the filer was updated to Ontap 7.2.3 we receive "
jcifs.smb.SmbException: Incorrect function".

This looks like a problem that should be fixed with jcifs-1.2.15. We tried every jcifs-version since then, but it still won't work.

It also didn't change when we moved from Websphere 5.1 to 6.1.

On an older filer with Ontap 7.0.6 it still works.

Netapp refuses to solve the problem since they think their software works correctly.

I found this link on the web desribing the same problem with jcifs-1.2.17 and forwarded it to the netapp support, but i'm not very hopeful.

http://www.nabble.com/SmbFileOutputStream-with-append%3Dtrue-misbehaving-on-a-certain-NAS-td14944774.html

Here is a part of the stacktrace

jcifs.smb.SmbException: Incorrect function.
      [10.12.07 10:36:07:983 IRST]   d5454d SystemErr     R   at
      jcifs.smb.SmbTransport.checkStatus(SmbTransport.java:583)
      [10.12.07 10:36:07:983 IRST]   d5454d SystemErr     R   at
      jcifs.smb.SmbTransport.send(SmbTransport.java:683)
      [10.12.07 10:36:07:983 IRST]   d5454d SystemErr     R   at
      jcifs.smb.SmbSession.sessionSetup(SmbSession.java:330)
      [10.12.07 10:36:07:983 IRST]   d5454d SystemErr     R   at
      jcifs.smb.SmbSession.send(SmbSession.java:269)
      [10.12.07 10:36:07:984 IRST]   d5454d SystemErr     R   at
      jcifs.smb.SmbTree.treeConnect(SmbTree.java:154)
      [10.12.07 10:36:07:984 IRST]   d5454d SystemErr     R   at
      jcifs.smb.SmbFile.connect(SmbFile.java:806)
      [10.12.07 10:36:07:984 IRST]   d5454d SystemErr     R   at
      jcifs.smb.SmbFile.connect0(SmbFile.java:772)
      [10.12.07 10:36:07:984 IRST]   d5454d SystemErr     R   at
      jcifs.smb.SmbFile.open0(SmbFile.java:837)
      [10.12.07 10:36:07:984 IRST]   d5454d SystemErr     R   at
      jcifs.smb.SmbFile.open(SmbFile.java:866)
      [10.12.07 10:36:07:984 IRST]   d5454d SystemErr     R   at
      jcifs.smb.SmbFileOutputStream.<init>(SmbFileOutputStream.java:142)
      [10.12.07 10:36:07:985 IRST]   d5454d SystemErr     R   at
      jcifs.smb.SmbFileOutputStream.<init>(SmbFileOutputStream.java:97)
      [10.12.07 10:36:07:985 IRST]   d5454d SystemErr     R   at
      jcifs.smb.SmbFileOutputStream.<init>(SmbFileOutputStream.java:67)
      [10.12.07 10:36:07:985 IRST]   d5454d SystemErr     R   at
      jcifs.smb.SmbFile.getOutputStream(SmbFile.java:2625)
      [10.12.07 10:36:07:985 IRST]   d5454d SystemErr     R   at
      de.bundesbank.esb.web.view.RootRiverView.renderToUrl(RootRiverView.java:134)

Does anybody know a solution or a workaround?

Best regards
Harald
_____________________________________________________
Harald Preczek
Deutsche Bundesbank
Zentralbereich IT
Produktmanagement Anwendungssysteme
Wertpapier, Kredit, Devisen, Risiko-Controlling, Depot
Tel: [phone] | Fax: [phone]
Email: harald.preczek@...
Homepage: www.bundesbank.de

(Embedded image moved to file: pic08793.jpg)


--
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese E-Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail oder von Teilen dieser Mail ist nicht gestattet.

Wir haben alle verkehrsüblichen Maßnahmen unternommen, um das Risiko der Verbreitung virenbefallener Software oder E-Mails zu minimieren, dennoch raten wir Ihnen, Ihre eigenen Virenkontrollen auf alle Anhänge an dieser Nachricht durchzuführen. Wir schließen außer für den Fall von Vorsatz oder grober Fahrlässigkeit die Haftung für jeglichen Verlust oder Schäden durch virenbefallene Software oder E-Mails aus.

Jede von der Bank versendete E-Mail ist sorgfältig erstellt worden, dennoch schließen wir die rechtliche Verbindlichkeit aus; sie kann nicht zu einer irgendwie gearteten Verpflichtung zu Lasten der Bank ausgelegt werden.
______________________________________________________________________

This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of  the material in this e-mail or of parts hereof is strictly forbidden.

We have taken precautions to minimize the risk of transmitting software viruses but nevertheless advise you to carry out your own virus checks on any attachment of this message. We accept no liability for loss or damage caused by software viruses except in case of gross negligence or willful behaviour.

Any e-mail messages from the Bank are sent in good faith, but shall not be binding or construed as constituting any kind of obligation on the part of the Bank.

[Michael B Allen]

On 6/6/08, harald.preczek@... <harald.preczek@...> wrote:

>
>
>  Hi,
>
>  we have an application running on IBM Websphere 5.1/6.1 (hosted on Sun
>  Solaris 10) using jcifs to access a fileshare on a netapp-filer via smb and
>  write files into a windows filesystem.
>
>  Since the filer was updated to Ontap 7.2.3 we receive "
>  jcifs.smb.SmbException: Incorrect function".
>
>  This looks like a problem that should be fixed with jcifs-1.2.15. We tried
>  every jcifs-version since then, but it still won't work.
>
>  It also didn't change when we moved from Websphere 5.1 to 6.1.
>
>  On an older filer with Ontap 7.0.6 it still works.
>
>  Netapp refuses to solve the problem since they think their software works
>  correctly.

Yeah, NetApp only does what it needs to do to satisfy Windows clients.
So even though protocolwise JCIFS is completely correct, if we don't
emulate Windows exactly, NetApp will very likely complain.

I managed to actually contact someone from NetApp and asked to get
access to their emulator for Linux. They said they never heard of
JCIFS and asked me to name some companies that used it. But after
providing a list I never received a reply.

>  I found this link on the web desribing the same problem with jcifs-1.2.17
>  and forwarded it to the netapp support, but i'm not very hopeful.
>
>  http://www.nabble.com/SmbFileOutputStream-with-append%3Dtrue-misbehaving-on-a-certain-NAS-td14944774.html

I still have those captures but I have no time for flying blind trial
and error BS. If someone comes up with a fix and verifies that it
works with NetApp that would help. Or if you can get me the NetApp
simulator for Linux that would work too.

Mike

--
Michael B Allen
PHP Active Directory SPNEGO SSO
http://www.ioplex.com/

[harald.preczek]

Hi,

i've tried jcifs 1.2.21 and found a different behaviour.

Until 1.2.19 we got an "incorrect function" now we have

[09.06.08 08:13:39:087 MEST] 00000023 SystemErr     R
java.lang.NullPointerException
             at
de.bundesbank.esb.model.report.CsvRenderer.renderToUrl(CsvRenderer.java:83)
             at
de.bundesbank.esb.webintra.controller.scheduler.SchedulerEinreichungReportController.execute(SchedulerEinreichungReportController.java:34)

             at
de.bundesbank.esb.webintra.controller.scheduler.SchedulerController.handleRequest(SchedulerController.java:45)

             at
org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:48)

             at
org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:875)

             at
org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:809)

             at
org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:476)

             at
org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:441)

             at
javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
             at
javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
             at
com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1068)

             at
com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1009)

             at
com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:145)

             at
com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(PageFilter.java:119)

             at
com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:55)

             at
com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:190)

             at
com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:130)

             at
de.bundesbank.esb.web.filter.GZIPFilter.doFilter(GZIPFilter.java:56)
             at
com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:190)

             at
com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:130)

             at
de.bundesbank.esb.web.filter.RedirectAfterPostFilter.doFilter(RedirectAfterPostFilter.java:54)

             at
com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:190)

             at
com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:130)

             at
com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:87)

             at
com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:771)

             at
com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:679)

             at
com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:539)

             at
com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:478)

             at
com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3357)
             at
com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:267)
             at
com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:811)
             at
com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContainer.java:1455)

             at
com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:115)
             at
com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:454)

             at
com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:383)

             at
com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:263)

             at
com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminators(NewConnectionInitialReadCallback.java:214)

             at
com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:113)

             at
com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)

             at
com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)

             at
com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)

             at
com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:136)
             at
com.ibm.io.async.ResultHandler.complete(ResultHandler.java:195)
             at
com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:743)

             at
com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:873)
             at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1473)

Is it just a change of behaviour?

I wanted to attach the NetApp emulator for Linux for Ontap 7.2.4, but it's
too big for our provider (50 MBytes). Shall I split the archive? Or can I
send it on a different way?

Greetings
Harald
_____________________________________________________
Harald Preczek
Deutsche Bundesbank
Zentralbereich IT
Produktmanagement Anwendungssysteme
Wertpapier, Kredit, Devisen, Risiko-Controlling, Depot
Tel: [phone] | Fax: [phone]
Email: harald.preczek@...
Homepage: www.bundesbank.de

(Embedded image moved to file: pic23990.jpg)


                                                                       
             "Michael B Allen"                                        
             <ioplex@...                                        
             >                                                          An
                                         "harald.preczek@..."
             07.06.2008 07:40            <harald.preczek@...>
                                                                     Kopie
                                         jcifs@...        
                                                                     Thema
                                         Re: [jcifs]                  
                                         jcifs.smb.SmbException: Incorrect
                                         function                      
                                                                       
                                                                       
                                                                       
                                                                       
                                                                       
                                                                       




On 6/6/08, harald.preczek@... <harald.preczek@...>
wrote:
>
>
>  Hi,
>
>  we have an application running on IBM Websphere 5.1/6.1 (hosted on Sun
>  Solaris 10) using jcifs to access a fileshare on a netapp-filer via smb
and
>  write files into a windows filesystem.
>
>  Since the filer was updated to Ontap 7.2.3 we receive "
>  jcifs.smb.SmbException: Incorrect function".
>
>  This looks like a problem that should be fixed with jcifs-1.2.15. We
tried
>  every jcifs-version since then, but it still won't work.
>
>  It also didn't change when we moved from Websphere 5.1 to 6.1.
>
>  On an older filer with Ontap 7.0.6 it still works.
>
>  Netapp refuses to solve the problem since they think their software
works
>  correctly.

Yeah, NetApp only does what it needs to do to satisfy Windows clients.
So even though protocolwise JCIFS is completely correct, if we don't
emulate Windows exactly, NetApp will very likely complain.

I managed to actually contact someone from NetApp and asked to get
access to their emulator for Linux. They said they never heard of
JCIFS and asked me to name some companies that used it. But after
providing a list I never received a reply.

>  I found this link on the web desribing the same problem with
jcifs-1.2.17
>  and forwarded it to the netapp support, but i'm not very hopeful.
>
>
http://www.nabble.com/SmbFileOutputStream-with-append%3Dtrue-misbehaving-on-a-certain-NAS-td14944774.html


I still have those captures but I have no time for flying blind trial
and error BS. If someone comes up with a fix and verifies that it
works with NetApp that would help. Or if you can get me the NetApp
simulator for Linux that would work too.

Mike

--
Michael B Allen
PHP Active Directory SPNEGO SSO
http://www.ioplex.com/




--
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail
irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und
vernichten Sie diese E-Mail. Das unerlaubte Kopieren sowie die unbefugte
Weitergabe dieser Mail oder von Teilen dieser Mail ist nicht gestattet.

Wir haben alle verkehrsüblichen Maßnahmen unternommen, um das Risiko der
Verbreitung virenbefallener Software oder E-Mails zu minimieren, dennoch
raten wir Ihnen, Ihre eigenen Virenkontrollen auf alle Anhänge an dieser
Nachricht durchzuführen. Wir schließen außer für den Fall von Vorsatz oder
grober Fahrlässigkeit die Haftung für jeglichen Verlust oder Schäden durch
virenbefallene Software oder E-Mails aus.

Jede von der Bank versendete E-Mail ist sorgfältig erstellt worden, dennoch
schließen wir die rechtliche Verbindlichkeit aus; sie kann nicht zu einer
irgendwie gearteten Verpflichtung zu Lasten der Bank ausgelegt werden.
______________________________________________________________________

This e-mail may contain confidential and/or privileged information. If you
are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail. Any
unauthorised copying, disclosure or distribution of  the material in this
e-mail or of parts hereof is strictly forbidden.

We have taken precautions to minimize the risk of transmitting software
viruses but nevertheless advise you to carry out your own virus checks on
any attachment of this message. We accept no liability for loss or damage
caused by software viruses except in case of gross negligence or willful
behaviour.

Any e-mail messages from the Bank are sent in good faith, but shall not be
binding or construed as constituting any kind of obligation on the part of
the Bank.

[harald.preczek]

We use FQDN.

But I tried just using the hostname and it won't work either.

Harald
_____________________________________________________
Harald Preczek
Deutsche Bundesbank
Zentralbereich IT
Produktmanagement Anwendungssysteme
Wertpapier, Kredit, Devisen, Risiko-Controlling, Depot
Tel: [phone] | Fax: [phone]
Email: harald.preczek@...
Homepage: www.bundesbank.de

(Embedded image moved to file: pic24353.jpg)


                                                                       
             tinius_paul@...                                        
             om                                                        
                                                                        An
             06.06.2008 23:54            <harald.preczek@...>,
                                         <jcifs@...>      
                                                                     Kopie
                                                                       
                                                                     Thema
                                         RE: [jcifs]                  
                                         jcifs.smb.SmbException: Incorrect
                                         function                      
                                                                       
                                                                       
                                                                       
                                                                       
                                                                       
                                                                       




Are you accessing the filer using the FQDN name? Just using the hostname
fixed it for us.

Paul

-----Original Message-----
From: jcifs-bounces+tinius_paul=emc.com@...
[mailto:jcifs-bounces+tinius_paul=emc.com@...] On Behalf Of
harald.preczek@...
Sent: Friday, June 06, 2008 5:21 AM
To: jcifs@...
Subject: [jcifs] jcifs.smb.SmbException: Incorrect function



Hi,

we have an application running on IBM Websphere 5.1/6.1 (hosted on Sun
Solaris 10) using jcifs to access a fileshare on a netapp-filer via smb and
write files into a windows filesystem.

Since the filer was updated to Ontap 7.2.3 we receive "
jcifs.smb.SmbException: Incorrect function".

This looks like a problem that should be fixed with jcifs-1.2.15. We tried
every jcifs-version since then, but it still won't work.

It also didn't change when we moved from Websphere 5.1 to 6.1.

On an older filer with Ontap 7.0.6 it still works.

Netapp refuses to solve the problem since they think their software works
correctly.

I found this link on the web desribing the same problem with jcifs-1.2.17
and forwarded it to the netapp support, but i'm not very hopeful.

http://www.nabble.com/SmbFileOutputStream-with-append%3Dtrue-misbehaving-on-a-certain-NAS-td14944774.html


Here is a part of the stacktrace

jcifs.smb.SmbException: Incorrect function.
      [10.12.07 10:36:07:983 IRST]   d5454d SystemErr     R   at
      jcifs.smb.SmbTransport.checkStatus(SmbTransport.java:583)
      [10.12.07 10:36:07:983 IRST]   d5454d SystemErr     R   at
      jcifs.smb.SmbTransport.send(SmbTransport.java:683)
      [10.12.07 10:36:07:983 IRST]   d5454d SystemErr     R   at
      jcifs.smb.SmbSession.sessionSetup(SmbSession.java:330)
      [10.12.07 10:36:07:983 IRST]   d5454d SystemErr     R   at
      jcifs.smb.SmbSession.send(SmbSession.java:269)
      [10.12.07 10:36:07:984 IRST]   d5454d SystemErr     R   at
      jcifs.smb.SmbTree.treeConnect(SmbTree.java:154)
      [10.12.07 10:36:07:984 IRST]   d5454d SystemErr     R   at
      jcifs.smb.SmbFile.connect(SmbFile.java:806)
      [10.12.07 10:36:07:984 IRST]   d5454d SystemErr     R   at
      jcifs.smb.SmbFile.connect0(SmbFile.java:772)
      [10.12.07 10:36:07:984 IRST]   d5454d SystemErr     R   at
      jcifs.smb.SmbFile.open0(SmbFile.java:837)
      [10.12.07 10:36:07:984 IRST]   d5454d SystemErr     R   at
      jcifs.smb.SmbFile.open(SmbFile.java:866)
      [10.12.07 10:36:07:984 IRST]   d5454d SystemErr     R   at
      jcifs.smb.SmbFileOutputStream.<init>(SmbFileOutputStream.java:142)
      [10.12.07 10:36:07:985 IRST]   d5454d SystemErr     R   at
      jcifs.smb.SmbFileOutputStream.<init>(SmbFileOutputStream.java:97)
      [10.12.07 10:36:07:985 IRST]   d5454d SystemErr     R   at
      jcifs.smb.SmbFileOutputStream.<init>(SmbFileOutputStream.java:67)
      [10.12.07 10:36:07:985 IRST]   d5454d SystemErr     R   at
      jcifs.smb.SmbFile.getOutputStream(SmbFile.java:2625)
      [10.12.07 10:36:07:985 IRST]   d5454d SystemErr     R   at

de.bundesbank.esb.web.view.RootRiverView.renderToUrl(RootRiverView.java:134)


Does anybody know a solution or a workaround?

Best regards
Harald
_____________________________________________________
Harald Preczek
Deutsche Bundesbank
Zentralbereich IT
Produktmanagement Anwendungssysteme
Wertpapier, Kredit, Devisen, Risiko-Controlling, Depot
Tel: [phone] | Fax: [phone]
Email: harald.preczek@...
Homepage: www.bundesbank.de

(Embedded image moved to file: pic08793.jpg)


--
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail
irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und
vernichten Sie diese E-Mail. Das unerlaubte Kopieren sowie die unbefugte
Weitergabe dieser Mail oder von Teilen dieser Mail ist nicht gestattet.

Wir haben alle verkehrsüblichen Maßnahmen unternommen, um das Risiko der
Verbreitung virenbefallener Software oder E-Mails zu minimieren, dennoch
raten wir Ihnen, Ihre eigenen Virenkontrollen auf alle Anhänge an dieser
Nachricht durchzuführen. Wir schließen außer für den Fall von Vorsatz oder
grober Fahrlässigkeit die Haftung für jeglichen Verlust oder Schäden durch
virenbefallene Software oder E-Mails aus.

Jede von der Bank versendete E-Mail ist sorgfältig erstellt worden, dennoch
schließen wir die rechtliche Verbindlichkeit aus; sie kann nicht zu einer
irgendwie gearteten Verpflichtung zu Lasten der Bank ausgelegt werden.
______________________________________________________________________

This e-mail may contain confidential and/or privileged information. If you
are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail. Any
unauthorised copying, disclosure or distribution of  the material in this
e-mail or of parts hereof is strictly forbidden.

We have taken precautions to minimize the risk of transmitting software
viruses but nevertheless advise you to carry out your own virus checks on
any attachment of this message. We accept no liability for loss or damage
caused by software viruses except in case of gross negligence or willful
behaviour.

Any e-mail messages from the Bank are sent in good faith, but shall not be
binding or construed as constituting any kind of obligation on the part of
the Bank.




--
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail
irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und
vernichten Sie diese E-Mail. Das unerlaubte Kopieren sowie die unbefugte
Weitergabe dieser Mail oder von Teilen dieser Mail ist nicht gestattet.

Wir haben alle verkehrsüblichen Maßnahmen unternommen, um das Risiko der
Verbreitung virenbefallener Software oder E-Mails zu minimieren, dennoch
raten wir Ihnen, Ihre eigenen Virenkontrollen auf alle Anhänge an dieser
Nachricht durchzuführen. Wir schließen außer für den Fall von Vorsatz oder
grober Fahrlässigkeit die Haftung für jeglichen Verlust oder Schäden durch
virenbefallene Software oder E-Mails aus.

Jede von der Bank versendete E-Mail ist sorgfältig erstellt worden, dennoch
schließen wir die rechtliche Verbindlichkeit aus; sie kann nicht zu einer
irgendwie gearteten Verpflichtung zu Lasten der Bank ausgelegt werden.
______________________________________________________________________

This e-mail may contain confidential and/or privileged information. If you
are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail. Any
unauthorised copying, disclosure or distribution of  the material in this
e-mail or of parts hereof is strictly forbidden.

We have taken precautions to minimize the risk of transmitting software
viruses but nevertheless advise you to carry out your own virus checks on
any attachment of this message. We accept no liability for loss or damage
caused by software viruses except in case of gross negligence or willful
behaviour.

Any e-mail messages from the Bank are sent in good faith, but shall not be
binding or construed as constituting any kind of obligation on the part of
the Bank.