navigation bar left navigation bar right

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

Forum Thread: Beta 3 error code 12031 (Vista)

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:
PSI

This thread has been marked as locked.
nilsgehrig Beta 3 error code 12031 (Vista)
Member 17th Mar, 2012 15:12
Ranking: 0
Posts: 3
User Since: 17th Mar, 2012
System Score: N/A
Location: CH
Since I installed Beta 3 on my Vista with SP2 I always see:
[03/17 14:55:41.378] Error in HttpRequest: status=499, statusText='Die Serververbindung wurde zurückgesetzt. ',winCode=12031

and

[03/17 14:55:39.375] GET /psi_api/3005/?action=agent_check&agent_version=3. 0.0.5&tz=-3600&fm=0x80000000&uid=vxFYvBUlIYaecbeba bda1bf5b3f6a76bxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx&ui =agent&langroup=ATLAS&host=OBELIX

[03/17 14:55:39.376] Request timeouts : 60000ms, 30000ms, 30000ms


The german text in the first log entry means "Server connection has been reset", which according Microsoft happens due to a timeout.

The parallel installation on W7 using the same squid proxy works absolutely fine.

Any idea or hint?

mogs RE: Beta 3 error code 12031 (Vista)
Expert Contributor 17th Mar, 2012 17:06
Score: 2265
Posts: 6,268
User Since: 22nd Apr 2009
System Score: 100%
Location: UK
@nilsgehrig

I'm almost sure I've seen another thread recently; mentioning squid proxy....can't find it to refer to at the moment. Secunia's policy regarding proxies hasn't altered tho', as far as I'm aware.

USE OF PROXY

Statement issued by a Secunia Official on 11th May 2011

For users using proxies, there is bound to be a range of unexpected issues.

As such, these are not going to be fixed, as the PSI does not support proxies, or systems running proxies.

Original 11:04 05/06/2011

As such it seems you are in luck with your W7 setup. Sorry I can't be more helpful....regards,

--
Was this reply relevant?
+1
-0
nilsgehrig RE: Beta 3 error code 12031 (Vista)
Member 18th Mar, 2012 11:14
Score: 0
Posts: 3
User Since: 17th Mar 2012
System Score: N/A
Location: CH
I bypassed squid and let the PC directly go to the internet. But the problem remains.
At least the steps "Determing files to scan" and "Scanning files" are skipped.
Was this reply relevant?
+0
-0
mogs RE: Beta 3 error code 12031 (Vista)
Expert Contributor 18th Mar, 2012 11:20
Score: 2265
Posts: 6,268
User Since: 22nd Apr 2009
System Score: 100%
Location: UK
@nilsgehrig

Have you looked thro' the settings in the FAQ's for inspiration ?.........:-
http://secunia.com/vulnerability_scanning/personal...

--
Was this reply relevant?
+0
-0
nilsgehrig RE: Beta 3 error code 12031 (Vista)
Member 18th Mar, 2012 12:12
Score: 0
Posts: 3
User Since: 17th Mar 2012
System Score: N/A
Location: CH
Last edited on 18th Mar, 2012 13:28
I did follow exactly all 6 steps. All was fine.
There was no service "Secunia Update Agent". I startet a command shell as admin and run sua.exe -i I had to set the user to "local system" instead of admin, rebooted the PC, controlled the services again. Update Agent was still there. But the scan diidn't work:
[03/18 11:51:36.364] WriteFile failed 0x000000e8
[03/18 11:51:36.368] Caught exception in accept at 627, error 0x000000e8
....
-- CheckIn Information --
CheckInInterval 60
LastCheckIn 03/18/12 11:53:34
NextInspection 03/18/12 11:53:28
ServerTime 01/01/80 00:00:00
REG_KEY_PATH SOFTWARE\Secunia\PSIA
[03/18 11:53:37.696] Unknown name in invoke:notifyCheckin
[03/18 11:53:37.696] Unknown name in invoke:periodic

The last one many times.


In the registry ..Software/secunia/sua I found a key "directory error" with the value:
Error reading ACLs on SUA directory, 0x00000002, Das System kann die angegebene Datei nicht finden.

The last german sentence means: System could not find the named directory
Was this reply relevant?
+0
-0

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
 MSSP
Technology Partners
References
 Reports
Webinars
Events
 About us
Careers
Memberships
Newsroom


Secunia is a member of FIRST Secunia is a member of EDUcause Secunia is a member of The Open Group Secunia is a member of FS-ISAC
 
Secunia © 2002-2014 Secunia ApS - Rued Langgaards Vej 8, 4th floor, DK-2300 Copenhagen, Denmark - +45 7020 5144
Terms & Conditions and Copyright - Privacy - Report Vulnerability - Disclaimer
follow Secunia on Facebook follow Secunia on Twitter follow Secunia on LinkedIn follow Secunia on YouTube follow Secunia Xing follow Secunias RSS feed follow Secunia on Google+