Browsing all articles tagged with Database Archives - Amer Atiyah, Microsoft Dynamics 365 Blog
0

It’s been so long and short years since I posted anything on my blog. So here you go, I’m blogging again.

If you faced an issue lately in connecting to Microsoft SQL Server database on the test machines of your Microsoft Dynamics 365 Finance & Operations cloud deployments, even after you added “.databse.windows.net” then your deployment might got effected by the latest release in August or September 2019.

We used to login with the LCS SQL Server credentials:

LCS Old Way

But we started to get the following error:

Cannot connect to spartan-*** .database.windows.net

Cannot open server ‘spartan-***’ requested by the login. Client with IP address ‘*.*.*.*’ is not allowed to access the server. To enable access, use the Windows Azure Management Portal to run sp_set_firewall_rule on the master database to create a firewall rule fore this IP addressor address range. It may ta up to five minutes to for this change to take effect. (Microsoft SQL Server, Error:40615)

Cannot connect to database

Now, Microsoft might have moved your database to different Azure SQL Servers.

To make it simple, you now still have to put the server name (from LCS) in the Connection fields in SQL Server Management Studio, and add “.databse.windows.net” but you need to go to Options button, and entering the Database name (from LCS). You should be able to connect.

Here you go in pictures:


NEW DB Connection LCS

Number 1 + “database.windows.net”:

SQL SerfverDatabase name

You should be able to connect now if you copied the right credentials like this:

Connected DB

Hope that helps.

0

I had a problem while running the SharePoint Configuration Wizard after installing WSS 3.0 SP2 that says:

Failed to connect to the configuration database.
An exception of type System.Data.SqlClient.SqlException was thrown.  Additional exception information: Access to module dbo.proc_getObjectsByClass is blocked because the signature is not valid.
System.Data.SqlClient.SqlException: Access to module dbo.proc_getObjectsByClass is blocked because the signature is not valid.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
.......

As it looks clear from the error, the wizard simply fails to connect to the database. (The database was installed as Express edition on the local machine and the OS was Windows Server 2008 R2.) After lots of tries to uninstall WSS 3.0 and reinstall it again and again… I have done the following:

  1. Un-installed Microsoft SQL Server Express Edition (from Programs and Features)
  2. Downloaded Microsoft SQL Server 2008 R2 Edition (http://www.microsoft.com/express/database/) and then installed it
  3. Installed WSS 3.0 SP2 as farm installation
  4. After the installation has finished, I got the SharePoint Configuration Wizard where I was able to choose the local database that I have just installed..

The wizard then ran just fine. Hope it will with you as well :)

9

This topic might not be new to most of you guys, but I always wondered how can I create a primary key to a Dynamics AX table?

You could easily create index in any table in Dynamics AX and you could specify that this index is “not duplicated”, which means that values of the field(s) should be unique among the table values. But this does not mean that you this index is a Primary Key index!

To create a Primary key you have to set the PrimaryIndex property in the list of that table properties.

PrimaryIndex Property

When you choose the PrimaryIndex property you have to set that index as “not duplicated”. Once you do that, you will have the icon of that index changed to be like this:

Primary Key Index Icon

6
Sometimes you might face an unexpected error when trying to insert new records to any of the Dynamics AX tables. The message you might have is like: Cannot create a record in Journal lines (LedgerJournalTrans). The record already exists.
You might also have tried to check the indexes of this table that shouldn’t be duplicated. And you got surprised when you are not violating those constraints, so there is no any rational reason why this error might appear.
After so many tries, I got to fix that error by:
  1. Backing-up my database (just in case that anything went wrong)
  2. Exporting the data of that table (from the AX Import/Export functionality)
  3. Deleting/Dropping the table from the Microsoft SQL Server Management Studio (by this all the data of course will be deleted)
  4. Opening the Dynamics AX client, going to: AOT –> Data Dictionary –> Tables –> LedgerJournalTrans –> Right clieck –> Synchronize
  5. Importing the data again to all companies (from the AX Import/Export functionality.

As you could see, I got this error in a very critical table that is the LedgerJournalTrans table. This table contained already posted lines and it was really headache for me to get it fixed. But fortunately I was able to fix it by following the previous steps. :)

Dynamics AX 2012 Event

Recent Posts

Tags

Archives

Random Testimonial

  • ~ Ahmad Al-Shanshoury, Senior Dynamics AX Consultant at Al-Fanar IT

    ahmed el shanshoury"I am pleased to be able to write this recommendation for Mr. Amer Atiyah, I was lucky to work with Amer during our implementation of Dynamics AX at AlOthaim company. Since the day one, I know him as an energetic and goal-oriented person Amer demonstrated a strong work ethic and a dedication to success. His efforts have produced high quality results time and time again.His extraordinary ability to analyze problems and outline necessary courses of action was invaluable, simply I can see Amer innovative, creative, intelligent and ambitious, in addition of his powerful Technical background. Seldom have I been able to recommend someone without reservation. It is a pleasure to do so in the case of Amer"

  • Read more testimonials »