Problem changing password using ADOX.Catalog.Users(User).ChangePassword

  • Thread starter Thread starter Neil Robbins
  • Start date Start date
Hi Neil,

I have check your code and database file. I found that the code is correct,
however, there might be something wrong with the .mdw file, because if I
use another pair of .mdb and .mdw file with the same code, it works fine.
With further research, I found this might be a known issue. You might have
to recreate the .mdw file and users with exact same account names and
personal identification numbers (PIDs) with current version of Access.
Please check the following KB article for reference:

http://support.microsoft.com/?id=824261

If anything is unclear, please feel free to reply to the post.

Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."
 
Hi Kevin,

Thanks for this and for all your other help, I'll try what you suggest and
post the results.

Neil R.
 
You're welcome, Neil. Thanks again for sharing your experience with us. If
you have any questions, please feel free to post them in the community. We
will try our best to help you.

Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."
 
Hi Kevin,

I'm back again with this one. I've tried what you suggested and followed the
suggestions in the KB article. I've also tried recreating the database and
security file from scratch in both Access 2000 and 2002. No joy at all -
still getting the same errors.

What I have done though is to write a separate application to edit passwords
&, with the correct privileges, to add/edit/delete users. For this I used
the same change password code that I have posted and sent to you. This works
fine with the exact same Access DB files that refuse to work with the
solution that I sent you. I'd be happy to send you a cut down demo copy of
this if you felt it might be useful.

This experience doesn't seem to fit the mould of the problem and solution
described in the kb article and seems to suggest to me, for what that's
worth, that there is something else going on - probably in the .net side of
this.

Thanks again for all your efforts & help,

Neil R.
 
Hi Neil,

Thank you for your update and Kevin's onging efforts on this issue!

As the project can work fine on Kevin's machine with the code from your repro package, but it failed on
yours even with a New .mdb and .mdw file, I suspect the problem could be a machine specific one. To
further isolate the problem, I suggest you taking the following actoins to see if the problem can be
addressed and suppressed:

1) Copy the Database (.mdb) and the Workgroup File (.mdw) to another machine. See if the project works
fine.

2) If the problem persists, we should also create a new database and new workgroup file to see if the
problem doesn't happen in the new pair of files on the new machine. If this fails to suppress the problem, it is
really a weird one as it didn't happen on Kevin's machine.

If the problem disappears on another machine, the problelm can be narrowed to a machine specific one. If
that, I recommend you apply the latest Jet 4.0 SP8 on the problematic machine to upgrade the Jet engine
version to suppress most of the Jet engine issue:

829558 Information About Jet 4.0 Service Pack 8
http://support.microsoft.com/?id=829558

3) If all of these cannot isolate/resolve the problem, we may establish the same environment to test this
issue fully and completely. This may take some time and we appreciate your patience and cooperation.

If there is any update Neil, please feel free to let Kevin and me know. We are here happy to be of
assistance!

Best Regards,

Billy Yao
Microsoft Online Support
 
Hi Billy,

Thanks for the reply - sorry for the delay in my response. I have been going
through double checking everything to try and ensure that what I have told
you is correct. To the best of my, limited, ability and knowledge it is. I
have answered your questions and points below in the body of your message.

Hope its of some use.

Regards,

Neil R.

"Billy Yao [MSFT]" said:
Hi Neil,

Thank you for your update and Kevin's onging efforts on this issue!

As the project can work fine on Kevin's machine with the code from your
repro package, but it failed on
yours even with a New .mdb and .mdw file, I suspect the problem could be a machine specific one. To
further isolate the problem, I suggest you taking the following actoins to see if the problem can be
addressed and suppressed:

Yet the same files work fine on the same machine with a different solution
written on the same machine, using essentially the same code.
1) Copy the Database (.mdb) and the Workgroup File (.mdw) to another
machine. See if the project works

Tried this already on a a win 2k sp4 machine - didn't work & now on a brand
new, fully updated XP Pro machine, still no joy.
2) If the problem persists, we should also create a new database and new workgroup file to see if the
problem doesn't happen in the new pair of files on the new machine. If
this fails to suppress the problem, it is
really a weird one as it didn't happen on Kevin's machine.

Done this on both the new machine (Win 2K) and the original machine (Win XP
Pro) - didn't work
If the problem disappears on another machine, the problelm can be narrowed to a machine specific one. If
that, I recommend you apply the latest Jet 4.0 SP8 on the problematic
machine to upgrade the Jet engine
version to suppress most of the Jet engine issue:

I have Jet 4.0 SP8 installed on both machines & MDAC 2.8 (from the April
MSDN mail out). I have just tested it out on a brand new XP PRO PC with all
available updates installed & still no joy.
829558 Information About Jet 4.0 Service Pack 8
http://support.microsoft.com/?id=829558

3) If all of these cannot isolate/resolve the problem, we may establish
the same environment to test this
issue fully and completely. This may take some time and we appreciate your
patience and cooperation.

You have my cooperation if you wish to embark on this. I am very busy with
work at the moment though so it may be that you too have to be a little
patient with me too, but I'll always try and get back to you as quickly as
practicably possible.
If there is any update Neil, please feel free to let Kevin and me know. We are here happy to be of
assistance!

Thanks, hope this has been of some use.
 
Hi Neil,

I have reviewed the whole issue thread. It seems that the error doesn't
exist in the code, since:
1) The code works fine on our side
2) The code works fine if you are using it in another application to open
another MDB file.

To further confirm it, I think you can try the following step:
In the erroneous project, try using the sample code to open another MDB
file to see if it has error. Just change the MDB file name in the
connection string.

If it has no error, then apparently the root cause is in the MDB file. It
is better for us to recreate the MDB file step by step to isolate the
problem.

If it still has error, then it is really strange. I may need to suggest you
ask for help from PSS. We may need to analyze memory dump, detailed repro
sample, and etc to look into it.

Thanks very much for your patience.

Best regards,
Yanhong Huang
Microsoft Community Support

Get Secure! ¨C www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.
 
Hi Yan-Hong,

sorry for the delay, been busy. I'll try what you suggest and let you know
tomorrow.

Regards

Neil R.
 
Hi Neil,

Thanks very much. I appreciate it very much.

Best regards,
Yanhong Huang
Microsoft Community Support

Get Secure! ¨C www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.
 
Hi Yanhong,

My apologies for the further delay, I will get this done before the end of
the Easter period (Monday).

Kind Regards,

Neil.
 
Hi Neil,

It is OK. We are here to support you at your convenience. :) Just test it
when you have free time.

Best regards,
Yanhong Huang
Microsoft Community Support

Get Secure! ¨C www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.
 
Back
Top