You have not selected a database

Maintex

Hi,

I have been using a test version of Navision Attain (v3.6) for the past week or so and I have been receiving the following error every now and again when logging in: Cannot create a file when one already exists...or something to that effect. However, I resolved this by restarting the test Navision instance on the server (I know it is not a good idea to not solve this issue but I have a deadline and the live system does not seem to have this issue).

Anyways, I have come to it today, got the same issue, restarted the service but now I get "You have not selected a database", and it continues to tell me how to select a database, which is how I got to this screen in the first place! So, I click File->Database->Open... and get the login screen, I enter the Server Name, User ID and Password (Database Name is blank) and I click OK, this is when I get this message box that I have not selected a database.

These settings have been working for the past two days at least (with the restarts of the service) but it is no longer working...please help!!!

Just in case this helps, when I start the service, in the event log I get the following warning:

The system failed to publish or update Navision Attain Database Server Service Connection Point in Active Directory.

The system returned the following error:
Access is denied.

kriki

Check this : http://www.mibuso.com/howtoinfo.asp?FileID=10

The error you receive is probably because the Windows user of the service probably has no permissions to the database-file.
You should add the permissions to the databasefile for that user (usally network service).

David_Singleton

Maintex wrote:

Hi,

I have been using a test version of Navision Attain (v3.6) for the past week or so...

...I have a deadline and the live system does not seem to have this issue...

Do I understnad that you are about to go live with ver 3.60?

:shock:

kriki

David Singleton wrote:

Maintex wrote:

Hi,

I have been using a test version of Navision Attain (v3.6) for the past week or so...

...I have a deadline and the live system does not seem to have this issue...

Do I understnad that you are about to go live with ver 3.60?

:shock:

I missed that one! :oops:

DenSter

I think he's having this issue on a test server that he is trying to replicate the live environment on, and he's having this problem on the test server but not on the live server.

David_Singleton

DenSter wrote:

I think he's having this issue on a test server that he is trying to replicate the live environment on, and he's having this problem on the test server but not on the live server.

Hmm its very unclear int he original post, but you could be right. The question to me would be why you woudl have such a strict deadline for a test system that is already probably 5 years late. :-k