Anybody have a clue what this is all about? DPX opens OK and this error message opens in a separate window.
Printable View
Anybody have a clue what this is all about? DPX opens OK and this error message opens in a separate window.
Gary, Magix probably forgot to switch on their nag server or forgot to update its credentials.
Acorn
I am seeing this too.
Ray
possibly a north american server then...
I'm in UK and am getting this message.
fair enough
I'm not, I'm in yorkshire [not getting the message that is... :)]
I was but not now, prog. was creating another icon which gave that message but not doing that now.
I'd be grateful for some clarification as I still have the problem and am unsure what to do.Quote:
Originally Posted by wizard509
acorn would know better than I, but as long as the program works ok there is nothing to do as far as I can see, it is a magix [background] server error and will sort itself out
I am still have this screen pop up.
Xara is working fine and I verified that the content catalog is working also.
It's just something on Magix end and does not affect operation.
Maybe they are trying to push out an Update to Xara Pro ( we can only wish :eek:)
Ray
It is not important to you.
It is damaging to Magix as it hasn't noticed or cared.
It is typically only for marketing; not updates will be notified this way.
Magix either does not have the monitoring in place or the staff are just robots who have no clue what to check, if they should check and, importantly, why they should check.
It is usually a server has overrun its log space or some configuration has died.
It might be an expired security certificate that keeps on popping up like it does to us when we stop renewing.
Just its own medicine back on itslef.
I am not getting the problem as I have disconnected Magix from my applications, redirected links to nicer places and switched to Xara Pro+ into the bargain.
Acorn
thanks
I checked with both my installed vers, one that is blocked in firewall, and the one that is not, did not get this either way
Rob thinks it's fixed now and that Magix was doing something, but he has no idea what and Magix probably does not either.
Having the same message here in Mexico (probably using US servers).
I confirm Ray's (@RKissane) post that the programs (WDP17, P&GD17) are functioning perfectly.
Greg