profile information stored somewhere

burdee64

Hello all,

I'm facing a curious problem. Ever since yesterday (and out of the blue) I receive some info-error when opening the salesTab. The error is not very conclusive, it checks every salesTable record for locationId and find some mismatch... But the error is not the real problem I guess...

The funny part of it all is: this error is only occurring with my personal account.
Other users don't get this error.

And additionally: It only occurs in our Development-environment, while the Production-environment is error-free...

I have reset all usersettings in Axapta to default, and closed Axapta.
Then I deleted the OAC file on my profiles folder: Local Settings / Application Data... (Cashing file)
Then starten Axapta again. No difference.. Problem still occurs.
Rebooted PC and logged in with different username: Axapta runs smooth.
PC logged out and logged in under my own account.. Problem exists.
Then to another PC: logged in with my account: problem exists.

I even restored the database from our PROD system (problem occurs in DEVELOPMENT) to this dev. system. No differences.

So the problem seems to be some setting somewhere stored in my Windows profile.
I dont have a clue where to look further.
It seems the last thing I might do is to remove my windows account and create a new one. But that's a task I don't wanna do yet.

Does any of you have a hint for me?

Specifics:
Windows 2003 serverpool
(No roaming profile)
XP-pro PC's
Axapta 3.0 SP3
Three tier
Prod and Dev on same AOS server, and on same SQL server

Thanks in advance.

saravananjay

If you are accessing the Application and database through AOS which resides in different server which is not your client.
Try reinstalling your client and connect to the same application and database if you havent tried this.

If there is problem with salestable in particular, drop data from the slaestable try creting a new record and try accessing it.

Harish

Hi Bert,

It is not clear from your message what info error you get.

You had mentioned that you get this message only against your login. Perhaps while coding did you or somebody checking for user login and throw an info message against your login?

Other thing you might want to do is - create a breakpoint on the info class -> add method and then open the SO form. This will give a clue about the where abouts of this info error. Hopefully from here you can check why Ax pops up info error only against your login.

Regards,