Odd permissions problem - Microsoft Accounting
osaddict
London, UK
If I create a new user on XP (or Vista) and said user account has a password, all is fine, I can access Microsoft Accounting Professional as usual...
However, if I ADD a password to an existing account, which has been accessing Microsoft Accounting and log out/in again and try to open the same company it whinges that the company may not exist or I may not have rights to open it.
Anyone have any ideas? - I tried the same thing on Vista and XP - with the same results - in each case the user account I was trying to add a password to was a Computer Administrator.
However, if I ADD a password to an existing account, which has been accessing Microsoft Accounting and log out/in again and try to open the same company it whinges that the company may not exist or I may not have rights to open it.
Anyone have any ideas? - I tried the same thing on Vista and XP - with the same results - in each case the user account I was trying to add a password to was a Computer Administrator.
0
Comments
I've looked at the file the accounting software is using to connec to the db - it's looking to the correct DB and if I try to ping the machine it's on it works fine. (With or without a password on the user account)
Can anyone think of any other things I can try to ascertain if its an XP(or Vista) issue or an accounting software issue?
Then in each case was the program installed under that admin account and then the password added after or do you have multiple admin accounts on the same computer and it's happening on each of them?
If it's the former I'd guess that the install is tied to the admin account somewhere in the program and a change in the admin account password isn't replicating to the Accounting software.
User account A:
created eons ago (early 2007 perhaps) No password, accounting pro installed early 2008.
Works fine.
Add a password for user account A (now) - get error above.
User account B:
Created yesterday, as admin, with password - accounting works fine!!
There is an account on PC A which has the same username as the accounting server - it was created also ages ago. If you give this account a password other than the same one as on the sever it fails, give it the server one and it's fine!
http://support.microsoft.com/kb/911184/en-us?spid=13056&sid=global
Describes a similar problem.
The simple file sharing is indeed turned off.
Now, I would beleive this article and just be irritated, however, it mistifies me that I can create a NEW user account with any username and password and it will connect fine, but old accounts do not play ball!
The solution, one would think, is to create a new user account and access it from there - but that's quite a headache as it means moving all the users stuff over - browser settings, passwords, bookmarks, files, years of emails, outlook client settings etc.
One other solution that may work would be to uninstall your accounting software, fix the user accounts reinstall the software and import the database back in.
Oh one other thing I thought of. If this is a database have you checked in the odbc settings for those users and checked how their connector was setup.
I know when I set up Outlook on a laptop for one of these users it took a good few hours for it to pull everything down and be fully up to date and usable.
tbh I think the issue is domain related (in so much as we are not on one), from the accounting package it looks like you can connect as a 'guest' - hence why non passworded accounts seem to work - or as a user with the same username and password as the server - i.e. there are 2 'categories' of user - and it will not let you add new ones if you supply the PC name etc as it cannot see them (yet you can ping them from the machine in question!)
This logic works fine until you remember that newly created users work fine!
I suppose I could try installing a demo of the accounting software on my pc (never been used for it) to see if it would be possible to uninstall/reinstall and connect - as this would probably be less work than moving the user accounts... I think...
Now as for the rest of the permissions. I'm only guess, again never used and and have no familiarity with it. I'm just thinking on how other database programs I've used work.
The demo trial is probably a worthwhile test regardless...
Ours is offsite, and the connection is pretty slow :/
The do, and they were using it when we migrated from IMAP to Exchange.
Agreed.
Setting up other nonsense will take its time though - the programs installed on just their user accounts...
I've decided to knock the trial on the head - I don't think it will be that helpful, as you say.
As I said before I am still convinced its the fact that we are not in a domain that's causing the problems - the accounts server (just a xp pro box) cannot see the other machines on the network so clients have to connect to it using the same details...
Why does irritating crap like this have to happen so close to Christmas!!
Just found out I will have to do 10 desk moves on Monday too to prepare for people moving departments in the new year!!
Which would mean the odbc connector isn't setup right in the first place. But again that's also thinking back to a domain environment where everything rolls through.