Re: Trouble using Terminal Server (RDP) with SQL 2005 Express (WebInspect 7) (303 Views)
Reply
Advisor
chardmon
Posts: 33
Registered: ‎10-19-2006
Message 1 of 3 (348 Views)

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
Occasional Contributor
APBR
Posts: 7
Registered: ‎05-09-2013
Message 2 of 3 (315 Views)

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

 

Respected Contributor
HansEnders
Posts: 605
Registered: ‎07-01-2008
Message 3 of 3 (303 Views)

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/highli...

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
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.