Solved Extension import fails with "commit failed on transaction Extensionimport"

[Wave-Lengths]

Hi All,

I have just installed a fresh install of 3CX V 16.0.6.655 on Debian 9.

When trying to import my extensions from CSV I get an error "commit failed on transaction Extensionimport" on the bottom right of the screen.

Any suggestions would be appreciated?

 

[JohnS_3CX]

Hi,

Can you create extensions using the normal method?

Were you trying to import extensionnumber that already exist?

Does your CSV comply with the type of PBX you created? (digit length)

 

[Wave-Lengths]

Hi,

Creating extensions using the normal method is working.
All extensions in the CSV are new extensions.
All extensions are 4 digits long.

The only difference to my previous imports that I have done is that I am pre-including the phone details, MAC, interface, model template and settings.

 

[JohnS_3CX]

Ok create one single extension normally, and include everything you need it to have.

Then export it on its own, and delete it from your PBX.

The try to import it back and see if this time it succeeds

If it does, then all that needs to be done is to compare the entry in the single list VS your original entry in the big list to see what the difference is, and adjust the rest accordingly.

 

[Wave-Lengths]

Hi John,

It looks like something has gone wrong. I have created an extension normally, added everything i need and exported just that extension as suggested. However now I am unable to delete that extension.

 

[Wave-Lengths]

Wait, that looks like it worked now. I have switched to using a private window as my browser was not refreshing the extension list.

Will compair to the long list and try again shortly and let you know how it goes.

 

[JohnS_3CX]

Ah ok it may have been a browser cache issue then

I would recommend to log in with the latest version of Chrome V86.x just to be sure.

 

[Wave-Lengths]

I have copied all details from the "template" extension (Except MAC and extension number and name) for all new extensions and im getting the "commit failed on transaction Extensionimport" again

 

[JohnS_3CX]

Understood. How many extension in total and how big is the file in kbytes?

 

[Wave-Lengths]

52 Extensions, 88KB file

 

[JohnS_3CX]

Ok we can check more in depth in this case:

1. Go to Activity Log
2. From Settings, switch to Verbose logs and restart all services
3. Log back in when ready, and try to import the file (replicate the issue)
4. Go to Activity Log again, click Logs, Instance, 3CXConfServicexxx-xx-xx.xxxx.log and download it

Send me a private message with a link to download the CSV and the Log file mentioned above and we can take a look at what is causing this behavior.

 

[Wave-Lengths]

Hi John,

I have found the issue. And its a stupid one. There were 2 extensions that shared the same extension number causing the entire import to fail.

It's one of those situations where I was blindly relying on the list that was sent through to me.

 

[JohnS_3CX]

No worries it happens sometimes

Glad to hear all is well now!