Actually, there appears to be ongoing Denial of Service issues on the NIST Site causing intermittent 503 errors.  If you retry the update manually a few times it should go through.  I presume NIST is working to address the root cause of issues seen on their site. 

From your own link.....

"We are aware of availability issues with the NVD API Endpoints and are working to resolve them."

And "please ensure that you or the tools you use have the latest schema files, which were recently updated" , are we updated ?

OK, I found it https://www.novell.com/documentation/zenworks-24.2/zen_cve_reference/data/zen_cve_reference.html , we are set for API 2.0

Not sure, why the manual way of updating CVE feed is gone.

There should be a "Run Now" Option....

I think I did notice if I "Canceled".....I had to exit out of that page and go back to see "Run Now" again.

If you manually hit the Web Site shown for your Feed with a browser....

You will intermittently see a 503....It seems to come and go for periods of time.

It was not working at all for me...then it was for a while....then not again.....that was Yesterday Afternoon when I was digging into things.

I would test via a browser before I tried to run the update in the ZCC...since it was not totally random....just longer stretches of good or bad.

No Craig I was talking about manual import, that was possible in 2000 U2. Should be added back, I'm still unable to get CVE DB updates.

There is no "Last successful sync" to see if the sync finished without problem. 

If you don't have any past success.....

Maybe you need to configure the Proxy for CVE

https://www.novell.com/documentation/zenworks-23.4/pdfdoc/zen_cve_reference/zen_cve_reference.pdf

Some details here...

If that does not help...I would open a case on why it's failing.  At worst, it should be intermittent over the last few days.

Craig thanks for reply. Yes I opened case #02912616, because every sync is a failure. Don't have proxy. 

Where in there did you find the way to check the schema?  I've been though this, a couple of times, and don't see it.  I see the source you posted of what it should be, but haven't figured out where to compare it too, to make sure it is updated correctly.

Or did you just assume that everything being set correctly was good enough?

I started digging after you hit this, and the CVE count at our client kept dropping a lot, and I didn't think we made that much of a difference patching.   Rest of our CVE subscription looks good otherwise.

FYI....The reason you cannot do manual updates like older versions is instead of just a giant zip....we can download changes.

For Example - After the initial synch, we can request updates/changes that occur between that date and now instead of needing to redownload the entire CVE DB each day as we did years ago.