I'm using the standard WNetAddConnection2 API call in my code.  If I run it
in the load event of a windows form, then everything works fine.  If,
however, I try to use it in the OnStart event of a windows service then the
first time I run it it works fine, but when I restart the service, it fails
with error 85 - ERROR_ALREADY_ASSIGNED.  If I restart the machine then it
again works fine the first time the service runs, but again fails when the
service restarts.

I've tried adding a call to WNetCancelConnection2 before the connect
attempt.  That is failing with error 2250 - ERROR_LOCAL_DRIVE

To keep this post manageable, I haven't included my own code as I don't
think it's necessary.  If someone does want to see it the then let me know
and I can post it.  The basic connection code is available here
http://www.*-*-*.com/

If anyone else has come across this problem in a service, then I'd love to
hear any ideas.

Thanks.

--
For real reply address, lose the cash
www.realuk.co.uk

If you make a persistent connection by passing CONNECT_UPDATE_PROFILE then the
connection will be available in the second attempt and thus you will get that
error. You can pass null here if you want to connect manually everytime through
your service.

Hope this helps!
Bharat Patel
Microsoft, Visual Basic .NET and C# .NET

This posting is provided "AS IS" with no warranties, and confers no rights.
Please reply to newsgroups only. Thanks.              

I've tried both CONNECT_UPDATE_PROFILE and 0, but I hadn't tried null.  I'll
give it a go tomorrow.  Thanks for the idea.

--
For real reply address, lose the cash
www.realuk.co.uk

No.  Still not working.  I was originally passing 0 as the flags value for
the connection.  I assume that's what you mean by null (as it's a
non-optional integer).

Any other ideas?

--
Rob Oldfield
www.realuk.co.uk

Rob,

Right after the call to WNetAddConnection2 API, add an If statement and check
the returncode for ERROR_ALREADY_ASSIGNED. If it is true, just continue
normally.

Hope this helps!
Bharat Patel
Microsoft, Visual Basic .NET

This posting is provided "AS IS" with no warranties, and confers no rights.
Please reply to newsgroups only. Thanks.              

No.  That doesn't work either.

I currently have just about everything in try/catch blocks so that I can
track what's going on.  Something like...

try
    makeconnection
end try

try
    write to share via mapped drive
end try

try
    write to share via UNC
end try

...with extra catch lines to enable me to write messages to an event log for
debugging.  When the connection fails with error 85 then the attempt with a
mapped drive comes back with "The filename, directory name, or volume label
syntax is incorrect", the the UNC attempt gives me "Logon failure: unknown
user name or bad password"

--
Rob Oldfield
www.realuk.co.uk

You may want to close the connection when the service is stopped using
WNetCancelConnection2 API.

Hope this helps!
Bharat Patel
Microsoft, Visual Basic .NET

This posting is provided "AS IS" with no warranties, and confers no rights.
Please reply to newsgroups only. Thanks.              

Yes.  That does the job.  I'd actually just figured it out when I saw this
post.  I'd tried disconnecting as the first thing in the start code, but
that also failed.  It does actually make sense, when I think about it, to
close down the connection when the service stops - just general good
housekeeping.

Many thanks for the ideas Bharat.

--
Rob Oldfield
www.realuk.co.uk