cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
AEE_IT
Level 4

Empty manifest file

Dear all,

we are facing an issue downloading a package: manifestFile string is empty.

The strange thing is that the same package was working yesterday. Today we tryed to create a new package but the behaviour is the same.

We had a similar issue in the past, it was related to ECCN, ENC and CCATS code. I checked them but seems are ok.

 

Please could you check what is happening?

 

Thank you so much!

0 Kudos
(6) Replies
jberthold
Revenera Moderator Revenera Moderator
Revenera Moderator

Hi @AEE_IT ,

Can you please provide the REST body for your Update Request so I can try to reproduce?

Best regards,

0 Kudos

Dear @jberthold ,

 

thanks a lot for your quick reply.

 

Here below the body:

{
"id": "Lodigiani-02",
"idType": "STRING",
"language": 1033,
"platform": "WIN64",
"publisherName": "amada",
"updateFromPkgId": "MachineLink4.4.8.4"
}

 

Thank you and best regards

0 Kudos

Dear @jberthold ,

about the previous body, we tryed to remove and upload again the file and now it works.

You can check using following body:

{
"id": "TestAML001",
"idType": "STRING",
"language": 1033,
"platform": "WIN64",
"publisherName": "amada",
"updateFromPkgId": "Updater1.3.8.5"
}

Here manifestFile is empty.

From my point of view there are some infrastructure issues, we are facing some random Internal Server Errors on the portal...

Regards

 

0 Kudos

Another example is:
{
"id": "TestAML001",
"idType": "STRING",
"language": 1033,
"platform": "WIN64",
"publisherName": "amada",
"updateFromPkgId": "AMLTest4.4.8.4"
}
0 Kudos
jberthold
Revenera Moderator Revenera Moderator
Revenera Moderator

Hi @AEE_IT ,

We originally got the empty manifest as well.  While looking into it further it looks as though you made some changes and  got it working as I now get the download URLs.

Best regards,

0 Kudos

Dear @jberthold,

the only thing we've done is create a new file and upload again the .exe file.

We needed it and we had to proceed with our activities.

Anyway, seems strange what happend. Could be a problem of FNO services? We didn't edit the configuration of entitlements, devices and so on, just created a new file. 

Could be that something went wrong during FNO internal procedures?

Thanks

0 Kudos