Secunia CSI7
Advisories
Research
Forums
Create Profile
Our Commitment
PSI
PSI API
CSI
OSI
xSI
Vulnerabilities
Programs
Open Discussions
My Threads
Create Thread
Statistics
About

Forum Thread: Publish CSI Agent Package error

You are currently viewing a forum thread in the Secunia Community Forum. Please note that opinions expressed here are not of Secunia but solely reflect those of the user who wrote it.

This thread was submitted in the following forum:
CSI

This thread has been marked as locked.
csi6@reykjanesbaer.is Publish CSI Agent Package error
Member 22nd Mar, 2014 13:46
Ranking: 0
Posts: 1
User Since: 1st Jan, 1970
System Score: N/A
Location: N/A
Hi
I´m create CSI Agent Pacekage and get this error when I publish it:

Failed to publish package.

Code: -2146233079
Publishing operation failed because the console and remote server versions do not match.



r.danailov RE: Publish CSI Agent Package error
Secunia Official 2nd May, 2014 11:42
Score: 25
Posts: 173
User Since: 3rd Jan 2012
System Score: N/A
Location: Copenhagen, DK
Last edited on 2nd May, 2014 11:43
Hi,

Usually, this error occurs in scenarios where you are using Secunia CSI on a remote machine than the server you are publishing packages to. The error indicates that the Client's version of WSUS Administration console is either different version than the WSUS Server console, or these are the same version but these have different patch levels (one of the machines applied more hot fixes than the other).

Here are the possible reasons for this error occurrence:

1. You have installed Secunia CSI on a Windows XP / Vista / 7 / 2003 / 2008, but you are trying to publish package to a Windows 2012 server. This is mandatory to fail as WSUS on Server 2012 is a different version than any WSUS Administration console installed on the former versions.

Solution #1: You shall transfer the CSI on a Windows 8 machine if your WSUS/SCCM is on Server 2012. If you are using Server 2012 R2 for your WSUS/SCCM, then you need the CSI on Windows 8.1, or alternatively installed directly on top of your Server 2012 R2.

2. You may get this message if you are using Windows Server 2012 R2, but you have CSI installed on any earlier version than Windows 8.1. In this case, Windows 8 may also fail to connect, an issue on the Microsoft end. Solution is the same as #1 stated above.

3. You are using WSUS on Server 2003/2008, and your CSI is installed on a remote XP / Vista / 7 / 2003 / 2008. The WSUS Administration console on the client is the same version number as the WSUS server. The CSI continues to fail with this awkward error.

Solution #3:

a) Go to your WSUS/SCCM server, click Start, then enter appwiz.cpl
b) Click on View Installed Updates at the top left side of the screen
c) Browse to the bottom of the list and find the Windows Server Update Services hot-fixes.
d) Write down the KB numbers your server had installed (either KB2720211, or KB2734608, or both)
e) Go back to your CSI machine and navigate to the same place
f) See which of the KB numbers is missing on the machine and then download and install it.

Problem #3 shall be solved after equalizing the patch levels of the two machines.

Kind regards / Stay Secure
Rosen Danailov / Security+
Secunia Customer Support

This thread has been marked as locked.


 Products Solutions Customers Partner Resources Company
 
 Corporate
Vulnerability Intelligence Manager (VIM)
Corporate Software Inspector (CSI)
Consumer
Personal Software Inspector (PSI)
Online Software Inspector (OSI)
 Industry
Compliance
Technology
Integration
 Customers
Testimonials
 VARS
MSSP
Technology Partners
References
 Reports
Webinars
Events
 About us
Careers
Memberships
Newsroom


 
© 2002-2014 Secunia ApS - Rued Langgaards Vej 8, 4th floor, DK-2300 Copenhagen, Denmark - +45 7020 5144
Terms & Conditions and Copyright - Privacy - Report Vulnerability