Provisoning file could not be generated

Status
Not open for further replies.

saba

Bronze Partner
Advanced Certified
Joined
Mar 18, 2015
Messages
52
Reaction score
11
Hi
On prmise server 18 update 6 build 908 on windows

i m not sure it's since update 18 6 but i have thoses error in server log interface:

  • Provisioning file /provisioning/z9umzvpini/firmware/snom/snomD765.xml requested by 192.168.2.148 could not be generated
    3CX Template Parser ID: 30040 08/02/2023 08:47:51
  • Provisioning file /provisioning/z9umzvpini/firmware/snom/snomD765.xml requested by 192.168.2.125 could not be generated
    3CX Template Parser ID: 30040 08/02/2023 08:27:18
  • Provisioning file /provisioning/z9umzvpini/firmware/snom/snomD765.xml requested by 192.168.2.151 could not be generated
    3CX Template Parser ID: 30040 08/02/2023 07:52:45
  • Provisioning file /provisioning/z9umzvpini/firmware/snom/snom710.xml requested by 192.168.2.147 could not be generated
    3CX Template Parser ID: 30040 08/02/2023 04:15:21

and the phoen can't update.

is this a know issue ?

Thank you
 
Last edited:
Hello,

No this is not an issue. It is normal for those very specific messages to appear when you first provision a Snom.
They will go away once you send at least 1 firmware update to your Snom


But what do you mean the phone can't update?
- Model?
- Firmware currently on it?
 
We are also seeing this issue since the last update. We have phones that are no longer registered.
We had not had those errors before the last update (not that it was noticed).

Model - Snom D735
Firmware - 10.1.141.10
 
I've got the same issues after this update.
 
I've got the same issues after this update.
As above, if you are facing problems start a new thread. If you are just seeing the messages and wondering why they appear, please read my first reply.
 
I am getting the same error with Fanvil phones.
 
I'm seeing this with Fanvil X series phones as well.
The "Cannot generate file" errors are interleaved with "file generated" messages so I'm unclear if it fails-then-succeeds, or succeeds-then-fails, or it's succeeding for one phone and failing for the next... most confusing.
 
I'm seeing this with Fanvil X series phones as well.
The "Cannot generate file" errors are interleaved with "file generated" messages so I'm unclear if it fails-then-succeeds, or succeeds-then-fails, or it's succeeding for one phone and failing for the next... most confusing.
Yes, these will also be taken care of later in a later batch of firmware updates. The phones will stop asking for irrelevant files that 3CX doesn't require.
 
I've got the same issues after this update. Phones - Snom710 and Snom720
We have some this phones that are no longer registered outside office LAN.
 
Hi,
This issue is already fixed in Update 7 Alpha.
I have just tested yet on my lab environment.
 
I'm still getting this error on Update 7. Do I have to wait for a new firmware update for this to go away?
 
Im also having this issue.. 18.0 U6 908

Just moved a load of phones to a new site with an SBC and cant get the phones to provision.

Yealink T42S 66.86.0.5
 
Everyone still having issues, please upgrade to V18 Update 7 which is now out and let us know.

FYI - Some messages that may appear which are not really errors, will appear in blue as Informational
 
Everyone still having issues, please upgrade to V18 Update 7 which is now out and let us know.

FYI - Some messages that may appear which are not really errors, will appear in blue as Informational
Is there no other way around it? I've got QCB waiting and i'll lose them.

How come these phones arent picking up their provisioning files?
 
Is there no other way around it? I've got QCB waiting and i'll lose them.

How come these phones arent picking up their provisioning files?
You have to investigate - we don't have any of your specific details on the matter.
Are you using a 3CX FQDN and certs or custom?
 
You have to investigate - we don't have any of your specific details on the matter.
Are you using a 3CX FQDN and certs or custom?
I've opened a ticket.

It's a 3CX FQDN
 
I've opened a ticket.

It's a 3CX FQDN

Ok in this case support will investigate for you and we will see how it goes.

If you want in the meantime, try to delete a phone from an extension, then factory reset and assign it again from the MC.

This will ensure the correct SBC gets selected.
 
I am having the same issues now with adding / reprovisioning using a Yealink T57W with the latest firmware so this issue does not seem to be with templates for just one or two manufacturers.
 
I am having the same issues now with adding / reprovisioning using a Yealink T57W with the latest firmware so this issue does not seem to be with templates for just one or two manufacturers.
Please start a new thread under the yealink section, and describe your issue, firmware version, actions you did etc.
 
Status
Not open for further replies.

Members Online Now

Forum statistics

Threads
111,832
Messages
589,283
Members
164,662
Latest member
DejanMDS