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: PSI 2 and 3 stopped working

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.
christrahlendorff PSI 2 and 3 stopped working
Member 17th Feb, 2013 21:33
Ranking: 0
Posts: 3
User Since: 16th Feb, 2013
System Score: N/A
Location: DE
Last edited on 17th Feb, 2013 21:34

Hi,

my PSI 2.x stopped working for at least a week.
At every scan it stopped 68%.
So I decided to upgrade to PSI 3.0 but it ifininitly scanned as well.
Supsequently deinstalled it, deletetd every Secunia folder and every Secunia related registry entry and redownloaded the PSI 3.0 Setup.

Since then I tried it a few times without success.
The PSI log after an scan that took several hours.
[...]
[02/16 23:21:28.555] NewFiles contains 52 files
[...]
[02/16 23:49:36.997] NewFiles contains 52 files
[02/16 23:49:37.746] Stopping 'Secunia PSI Agent' service
[02/16 23:49:37.839] Unloading filter driver
[02/16 23:49:37.839] WriteFile failed 0x000000e8
[02/16 23:49:37.949] Detaching C:
[02/16 23:49:37.964] Detaching X:
[02/16 23:49:37.964] Detaching E:
[02/16 23:49:37.964] Detaching F:
[02/16 23:49:40.959] Caught exception in accept at 627, error 0x000000e8
[02/16 23:49:40.959] Caught exception in accept at 627, error 0x000000e8
[02/16 23:49:43.409] Waiting for pipe to be done
[02/16 23:49:43.424] Closing pipe



mogs RE: PSI 2 and 3 stopped working
Expert Contributor 17th Feb, 2013 21:56
Score: 2265
Posts: 6,266
User Since: 22nd Apr 2009
System Score: 100%
Location: UK
@christrahlendorff

There were problems with Secunia servers for a few days, which may have been contributing to what you initially experienced. It may also be that a setting has gotten altered somewhere.

It's probably best to thoroughly check thro' your settings as per the FAQ's here :-
http://secunia.com/vulnerability_scanning/personal...

If you still find psi 3 fails following that.....it might be better to revert to psi 2.0..... which may have simply been another victim of the server problems.


Hope that helps..........regards.........

--
Was this reply relevant?
+0
-0
Maurice Joyce RE: PSI 2 and 3 stopped working
Handling Contributor 17th Feb, 2013 23:03
Score: 11581
Posts: 8,895
User Since: 4th Jan 2009
System Score: N/A
Location: UK
I note you have tried PSI 2 & that failed as well.

Open PSI 3>settings>scan individual drives - are your drives listed there with a tick (check mark) in Drive C (which I assume is your main drive) that is greyed out?



--
Maurice

Windows 7 SP1 64 Bit OS
HP Intel Pentium i7
IE 11 for Windows 7 SP1
16GB RAM
Was this reply relevant?
+0
-0
christrahlendorff RE: PSI 2 and 3 stopped working
Member 18th Feb, 2013 12:18
Score: 0
Posts: 3
User Since: 16th Feb 2013
System Score: N/A
Location: DE
Thanks for your replies, mogs and Maurice Joyce!

- I put secunia on the trusted site list but noch change.
My PSI 2 was working fine on my PC for years and I didn't upgrade because of the reduced amount of settings in PSI 3.
- The agent service is set on automatic and is running

- Open PSI 3>settings>scan individual drives -
If try to click on the option , nothing happens. The drive list on the right. doesn't appear.

Additional notes:
PSI infinitely scans at "Überprüfen auf veraltete Programme - Dateien werden überprüft"

My specs:
PSI 3.0.0.6001
Win 7 Pro 64bit, updated
Language: De
Antivirus AVG Free 2013
EMET 3.5
3 HDDs but I only scan my main drive.

Some more log:
[02/18 11:49:31.364] Pipe Server got incoming connection, feeding handle to child.
[02/18 11:49:31.364] Pipe Server accepting incoming connections
[02/18 11:49:31.406] WriteFile failed 0x000000e8
[02/18 11:49:32.963] Pipe Server got incoming connection, feeding handle to child.
[02/18 11:49:32.963] Waiting for pipe to be done
[02/18 11:49:32.964] Closing pipe
[02/18 11:49:32.964] Pipe Server accepting incoming connections
[02/18 11:49:33.013] notifyNewTray: server.setIcon('red')
[02/18 11:49:33.013] notifyNewTray: server.updateTooltip('Alle Ihre Programme sind aktuell')
[02/18 11:50:00.940] Waiting for pipe to be done
[02/18 11:50:00.940] Closing pipe
[02/18 11:51:43.443] Pipe Server got incoming connection, feeding handle to child.
[02/18 11:51:43.444] Pipe Server accepting incoming connections
[02/18 12:01:50.601] Checking in with server (psi3.secunia.com)
[02/18 12:01:50.602] Checkin reason : AutoInstallUpdates
[02/18 12:01:50.603] Connecting to psi3.secunia.com:443
[02/18 12:01:50.604] GET /psi_api/3006/?action=agent_check&agent_version=3. 0.0.6001&tz=-3600&fm=0x80000000&uid=qxRrZDfXRTb841 0ffea093314ec0c4d5xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx &ui=agent&langroup=WORKGROUP&host=WIND
[02/18 12:01:50.605] Request timeouts : 60000ms, 30000ms, 30000ms
[02/18 12:01:51.102] Starting filter driver
[02/18 12:01:51.103] -- Program Configuration --
-- Internal variables --
Version 3.0.0.6001
BinPath C:\Program Files (x86)\Secunia\PSI\PSIA.exe
BinDir C:\Program Files (x86)\Secunia\PSI
APPNAME Secunia PSI Agent
BINNAME psi.exe
-- Logging Settings --
LogLevel 2
LogFile C:\Program Files (x86)\Secunia\PSI\psialog.txt
LogFileMax 2097152
-- UserId options --
CAUser qxRrZDfXRTb8410ffea093314ec0c4d5xxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxx
-- Scan options --
ScanType 2
CheckOSUpdates 1
-- Customer Area options --
GroupName
-- Network Configuration --
API_SERVER_HOST psi3.secunia.com
API_SERVER_PORT 443
API_BASE_URI /psi_api/3006/?
-- Connectivity Options: --
RequestTimeout 120
NetworkImplementation WinInet
-- Proxy options --
ProxyURL
ProxyUser
ProxyPass <Not Set>
ProxyConfigState 0
-- Security options --
IgnoreInvalidCN 0
IgnoreUnknownCA 0
IgnoreCertRevocation 0
-- Service options --
InstallService 0
StartService 1
RemoveService 0
RunAsUser
RunAsPass <Not Set>
RunAsLocalSystem 0
DontWriteRegistry 0
Foreground 0
-- Computer Information --
ComputerName WIND
LanGroup WORKGROUP
CurrentUser SYSTEM
UserPrincipalName
-- CheckIn Information --
CheckInInterval 5400
LastCheckIn 02/18/13 12:01:50
NextInspection 02/08/13 15:58:30
ServerTime 02/18/13 12:02:12
REG_KEY_PATH SOFTWARE\Secunia\PSIA
RegConfKey HKEY_LOCAL_MACHINE
[02/18 12:01:51.608] Checking in with server (psi3.secunia.com)
[02/18 12:01:51.608] Checkin reason : AutoInstallUpdates
[02/18 12:01:51.608] Connecting to psi3.secunia.com:443
[02/18 12:01:51.609] GET /psi_api/3006/?action=agent_check&agent_version=3. 0.0.6001&tz=-3600&fm=0x80000000&uid=qxRrZDfXRTb841 0ffea093314ec0c4d5xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx &ui=agent&langroup=WORKGROUP&host=WIND
[02/18 12:01:51.609] Request timeouts : 60000ms, 30000ms, 30000ms
[02/18 12:01:52.108] Starting filter driver
[02/18 12:01:52.109] -- Program Configuration --
-- Internal variables --
Version 3.0.0.6001
BinPath C:\Program Files (x86)\Secunia\PSI\PSIA.exe
BinDir C:\Program Files (x86)\Secunia\PSI
APPNAME Secunia PSI Agent
BINNAME psi.exe
-- Logging Settings --
LogLevel 2
LogFile C:\Program Files (x86)\Secunia\PSI\psialog.txt
LogFileMax 2097152
-- UserId options --
CAUser qxRrZDfXRTb8410ffea093314ec0c4d5xxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxx
-- Scan options --
ScanType 2
CheckOSUpdates 1
-- Customer Area options --
GroupName
-- Network Configuration --
API_SERVER_HOST psi3.secunia.com
API_SERVER_PORT 443
API_BASE_URI /psi_api/3006/?
-- Connectivity Options: --
RequestTimeout 120
NetworkImplementation WinInet
-- Proxy options --
ProxyURL
ProxyUser
ProxyPass <Not Set>
ProxyConfigState 0
-- Security options --
IgnoreInvalidCN 0
IgnoreUnknownCA 0
IgnoreCertRevocation 0
-- Service options --
InstallService 0
StartService 1
RemoveService 0
RunAsUser
RunAsPass <Not Set>
RunAsLocalSystem 0
DontWriteRegistry 0
Foreground 0
-- Computer Information --
ComputerName WIND
LanGroup WORKGROUP
CurrentUser SYSTEM
UserPrincipalName
-- CheckIn Information --
CheckInInterval 5400
LastCheckIn 02/18/13 12:01:51
NextInspection 02/08/13 15:58:30
ServerTime 02/18/13 12:02:10
REG_KEY_PATH SOFTWARE\Secunia\PSIA
RegConfKey HKEY_LOCAL_MACHINE
[02/18 12:01:52.614] Checking in with server (psi3.secunia.com)
[02/18 12:01:52.615] Checkin reason : AutoInstallUpdates
[02/18 12:01:52.616] Connecting to psi3.secunia.com:443
[02/18 12:01:52.616] GET /psi_api/3006/?action=agent_check&agent_version=3. 0.0.6001&tz=-3600&fm=0x80000000&uid=qxRr*REMOVED*& ui=agent&langroup=WORKGROUP&host=WIND
[02/18 12:01:52.617] Request timeouts : 60000ms, 30000ms, 30000ms
[02/18 12:01:53.115] Starting filter driver
[02/18 12:01:53.116] -- Program Configuration --
-- Internal variables --
Version 3.0.0.6001
BinPath C:\Program Files (x86)\Secunia\PSI\PSIA.exe
BinDir C:\Program Files (x86)\Secunia\PSI
APPNAME Secunia PSI Agent
BINNAME psi.exe
-- Logging Settings --
LogLevel 2
LogFile C:\Program Files (x86)\Secunia\PSI\psialog.txt
LogFileMax 2097152
-- UserId options --
CAUser qxR*REMOVED*
-- Scan options --
ScanType 2
CheckOSUpdates 1
-- Customer Area options --
GroupName
-- Network Configuration --
API_SERVER_HOST psi3.secunia.com
API_SERVER_PORT 443
API_BASE_URI /psi_api/3006/?
-- Connectivity Options: --
RequestTimeout 120
NetworkImplementation WinInet
-- Proxy options --
ProxyURL
ProxyUser
ProxyPass <Not Set>
ProxyConfigState 0
-- Security options --
IgnoreInvalidCN 0
IgnoreUnknownCA 0
IgnoreCertRevocation 0
-- Service options --
InstallService 0
StartService 1
RemoveService 0
RunAsUser
RunAsPass <Not Set>
RunAsLocalSystem 0
DontWriteRegistry 0
Foreground 0
-- Computer Information --
ComputerName WIND
LanGroup WORKGROUP
CurrentUser SYSTEM
UserPrincipalName
-- CheckIn Information --
CheckInInterval 5400
LastCheckIn 02/18/13 12:01:52
NextInspection 02/08/13 15:58:30
ServerTime 02/18/13 12:02:14
REG_KEY_PATH SOFTWARE\Secunia\PSIA
RegConfKey HKEY_LOCAL_MACHINE
[02/18 12:06:56.904] Waiting for pipe to be done
[02/18 12:06:56.904] Closing pipe
[02/18 12:08:23.397] Pipe Server got incoming connection, feeding handle to child.
[02/18 12:08:23.397] Pipe Server accepting incoming connections
[02/18 12:08:39.052] Waiting for pipe to be done
[02/18 12:08:39.052] Closing pipe
Was this reply relevant?
+0
-0
Maurice Joyce RE: PSI 2 and 3 stopped working
Handling Contributor 18th Feb, 2013 13:40
Score: 11581
Posts: 8,895
User Since: 4th Jan 2009
System Score: N/A
Location: UK
All your hard drives should appear in Settings>Scan Individual Drives. It looks like PSI is in a loop looking for the drive to scan & report on.

I only know of a few instances of this behaviour which was published on this Forum.

It happened to my XP test machine. In my case the loss of drive access was caused by a Registry Cleaner. After many hours trying to sort it & give a solution to the Forum I gave up & formatted my drive.

The other user did not use a Registry cleaner but also failed to find a solution.

What I would do is:

Check your User ID. It looks like it is correct but given the fact that you have cleared out the registry it is worth checking all is still in order:

https://akkkug.bay.livefilestore.com/y1p1FS5on3fMx...


If that is correct try a reinstall using this link - http://secunia.com/PSISetup.exe

Just let it run - it will auto uninstall the old before installing the new. Have the drives returned in settings?

If not:

Navigate to PSI in Windows Explorer & delete the two log files.

https://akkkug.bay.livefilestore.com/y1pvpP2x8EfT0...


Now run a scan. Send that log file to Secunia Support as an attachment to see if they can troubleshoot it for you.

The support address is: support @secunia.com

--
Maurice

Windows 7 SP1 64 Bit OS
HP Intel Pentium i7
IE 11 for Windows 7 SP1
16GB RAM
Was this reply relevant?
+0
-0
christrahlendorff RE: PSI 2 and 3 stopped working
Member 18th Feb, 2013 20:43
Score: 0
Posts: 3
User Since: 16th Feb 2013
System Score: N/A
Location: DE
Good news, my PSI is back :)

I tried your ideas but nothing happend. I had a 50characters ID and the main registry entries seemed to be equal to my other pc. As well I tried PSI 2.

Thanks for your time.

My solution lies somewhere in my later actions:

1. I deinstalled PSI 3.
2. I searched for "secunia" in the registry in keys, values and data and deleted all of them.
Remark:In this step I deleted also some entries of EMET 3.5 rules about PSI and its services. (There was never a warning of EMET that PSI was causing errors.)
3. I cleared my %TEMP% folder
4. I searched for all files and folders on drive C:\ related to "secunia" application and deleted them.

5. I reinstalled PSI with a different Language (English instead of German)
6. PSI works again.

Was this reply relevant?
+0
-0
Maurice Joyce RE: PSI 2 and 3 stopped working
Handling Contributor 18th Feb, 2013 21:25
Score: 11581
Posts: 8,895
User Since: 4th Jan 2009
System Score: N/A
Location: UK
Last edited on 19th Feb, 2013 17:56
Pleased to see you are all fixed up.

On that basis, I will lock this thread for U sometime tomorrow unless U post back asking for it to be left open.

This will protect your mail box from possible update emails from "tag on" posts

Secunia Support can always reopen threads by applying by email to: support@secunia.com

EDIT: Thread locked at 1600 hour GMT

--
Maurice

Windows 7 SP1 64 Bit OS
HP Intel Pentium i7
IE 11 for Windows 7 SP1
16GB RAM
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
 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