WebInspect
Showing results for 
Search instead for 
Do you mean 

Trouble using Terminal Server (RDP) with SQL 2005 Express (WebInspect 7)

Highlighted
Advisor

Trouble using Terminal Server (RDP) with SQL 2005 Express (WebInspect 7)

ISSUE:

You attempt to connect to your WebInspect™ 7 machine from another
computer using the Microsoft Terminal Server Client connection utility.
The connection fails with the following error and you are unable to
launch your scan remotely.



"Scan Initialization Failed"





CAUSE:

This is a known issue from Microsoft regarding SQL Server 2005 Express instances.



The Local Security Authority (LSA) uses the remote session's token
for the SQL Server client's session token, and the remote session's
token is from session 1 while the SQL Server client's session token is
from session 0.





SOLUTION:

Microsoft has released a hotfix for this issue. Please see the
related knowledge base article at the following page for information on
obtaining the hotfix:



http://support.microsoft.com/kb/896613



Note that you will have to request access to the hotfix from Microsoft Support.





APPLIES TO:

WebInspect 7.x
2 REPLIES
Occasional Contributor

Re: Trouble using Terminal Server (RDP) with SQL 2005 Express (WebInspect 7)

Hi

 

I am using WebInspect 10.1 and I am seeing the above "Scan Initialization Error" issue when trying to start a scan.

I installed webinspect on a server and RDP to server.

 

Thanks,

Rathan

 

Honored Contributor

Re: Trouble using Terminal Server (RDP) with SQL 2005 Express (WebInspect 7)

This article will not apply to your error unless you are using SQL Express 2005 and XP SP1 with RDP. ;-) This is a SQL Express cache corruption issue.

Check my older posting here: http://h30499.www3.hp.com/t5/WebInspect/Unable-to-load-scan-list-from-SQL-Express/m-p/2395192/highlight/true#M568

I also added a new Tag to this forum as "webinspect_scan_initialization_error". You can use this to jump to all the relevant articles.

The basic fix is to exit WI and SQL Express, delete the SQL Cache folder, then restart those two and everything works fine.

-- Habeas Data
HP Fortify Customers-Only Forums – https://protect724.hp.com/community/fortify