open a ticket with solarwinds, there is a hotfix i believe that fixes this as I have seen it asked here before but I cant readily find the answer
There is a KB that talks about this, but the short answer is: it's easier if the Patch Manager server and the WSUS server are running the same (or similar) OS. So, if one of them is 2003/2008/2008R2 (which all use WSUS 3.x), for easiest use the other should be one of those OSs as well. If one of them is 2012/2012R2 (which both use WSUS 6.x) for easiest use the other shoudl be one of those OSs.
There IS a way that you can make it work if one of them is 2003/2008/2008R2 and the other is 2012/2012R2. For that, you would install a Patch Manager Automation Server Role on the WSUS server or another similar OS'd server. You'd then create an Automation Server Routing Rule that says "when i do a task to the WSUS server, use this specific automation server instead of the default one. That would allow for publishing even though one is running WSUS 3.x console and the other is running a WSUS 6.x console.