none
ESB Toolkit 2.0 Configuration - Network path not found (Exception from HRESULT: 0x80070035) RRS feed

  • Question

  • Hi,

    I am unable to configure ESB Toolkit on VPC running Windows 2003 Server SP2. x86. The VPC is not a part of DOMAIN group, so I've used locally created user names.

    I have installed all the prerequisites still I'm unable to configure the ESB appropriately. I am able to create/configure the EsbExceptionDb but while setting up the Exception Web Services I get the error: Network path not found (Exception from HRESULT: 0x80070035)
    Below is the log file extract.

     

    ESBConfigurationTool.exe Information: 0 : Checking Microsoft SQL Server Management Objects (SMO).
    ESBConfigurationTool.exe Information: 0 : The assembly 'Microsoft.SqlServer.Smo, Version=10.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' was found in GAC.
    ESBConfigurationTool.exe Information: 0 : The assembly 'Microsoft.SqlServer.SqlEnum, Version=10.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' was found in GAC.
    ESBConfigurationTool.exe Information: 0 : The assembly 'Microsoft.SqlServer.ConnectionInfo, Version=10.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' was found in GAC.
    ESBConfigurationTool.exe Information: 0 : Checking Microsoft ESB Guidance.
    ESBConfigurationTool.exe Information: 0 : The configuration source found was: ESB File Configuration Source
    ESBConfigurationTool.exe Information: 0 : C:\Program Files\Microsoft BizTalk ESB Toolkit 2.0\esb.config
    ESBConfigurationTool.exe Information: 0 : Loading: ExceptionManagementDatabase
    ESBConfigurationTool.exe Information: 0 : ExceptionManagementDatabase: Unconfigured
    ESBConfigurationTool.exe Information: 0 : Loaded: ExceptionManagementDatabase
    ESBConfigurationTool.exe Information: 0 : Loading: WebServicesException
    ESBConfigurationTool.exe Information: 0 : Executing script: checkWebServices.ps1 in view: WebServicesException with parameters: Key: webSiteName Value: 1, Key: vDirName Value: ESB.ExceptionHandlingServices,
    ESBConfigurationTool.exe Information: 0 : Executing script: checkWebServices.ps1 in view: WebServicesException with parameters: Key: webSiteName Value: 1, Key: vDirName Value: ESB.ExceptionHandlingServices.WCF,
    ESBConfigurationTool.exe Information: 0 : WebServicesException: Unconfigured
    ESBConfigurationTool.exe Information: 0 : Loaded: WebServicesException
    ESBConfigurationTool.exe Information: 0 : Loading: WebServicesCore
    ESBConfigurationTool.exe Information: 0 : Executing script: checkWebServices.ps1 in view: WebServicesCore with parameters: Key: webSiteName Value: 1, Key: vDirName Value: ESB.ItineraryServices,
    ESBConfigurationTool.exe Information: 0 : Executing script: checkWebServices.ps1 in view: WebServicesCore with parameters: Key: webSiteName Value: 1, Key: vDirName Value: ESB.ItineraryServices.WCF,
    ESBConfigurationTool.exe Information: 0 : Executing script: checkWebServices.ps1 in view: WebServicesCore with parameters: Key: webSiteName Value: 1, Key: vDirName Value: ESB.ItineraryServices.Response,
    ESBConfigurationTool.exe Information: 0 : Executing script: checkWebServices.ps1 in view: WebServicesCore with parameters: Key: webSiteName Value: 1, Key: vDirName Value: ESB.ItineraryServices.Response.WCF,
    ESBConfigurationTool.exe Information: 0 : Executing script: checkWebServices.ps1 in view: WebServicesCore with parameters: Key: webSiteName Value: 1, Key: vDirName Value: ESB.ItineraryServices.Generic.WCF,
    ESBConfigurationTool.exe Information: 0 : Executing script: checkWebServices.ps1 in view: WebServicesCore with parameters: Key: webSiteName Value: 1, Key: vDirName Value: ESB.ItineraryServices.Generic.Response.WCF,
    ESBConfigurationTool.exe Information: 0 : Executing script: checkWebServices.ps1 in view: WebServicesCore with parameters: Key: webSiteName Value: 1, Key: vDirName Value: ESB.BizTalkOperationsService,
    ESBConfigurationTool.exe Information: 0 : Executing script: checkWebServices.ps1 in view: WebServicesCore with parameters: Key: webSiteName Value: 1, Key: vDirName Value: ESB.ResolverServices,
    ESBConfigurationTool.exe Information: 0 : Executing script: checkWebServices.ps1 in view: WebServicesCore with parameters: Key: webSiteName Value: 1, Key: vDirName Value: ESB.ResolverServices.WCF,
    ESBConfigurationTool.exe Information: 0 : Executing script: checkWebServices.ps1 in view: WebServicesCore with parameters: Key: webSiteName Value: 1, Key: vDirName Value: ESB.TransformServices,
    ESBConfigurationTool.exe Information: 0 : Executing script: checkWebServices.ps1 in view: WebServicesCore with parameters: Key: webSiteName Value: 1, Key: vDirName Value: ESB.TransformServices.WCF,
    ESBConfigurationTool.exe Information: 0 : WebServicesCore: Unconfigured
    ESBConfigurationTool.exe Information: 0 : Loaded: WebServicesCore
    ESBConfigurationTool.exe Information: 0 : Loading: ItineraryDatabase
    ESBConfigurationTool.exe Information: 0 : ItineraryDatabase: Unconfigured
    ESBConfigurationTool.exe Information: 0 : Loaded: ItineraryDatabase
    ESBConfigurationTool.exe Information: 0 : Loading: Configuration
    ESBConfigurationTool.exe Information: 0 : The configuration source found was: ESB File Configuration Source
    ESBConfigurationTool.exe Information: 0 : C:\Program Files\Microsoft BizTalk ESB Toolkit 2.0\esb.config
    ESBConfigurationTool.exe Information: 0 : The configuration source found was: ESB File Configuration Source
    ESBConfigurationTool.exe Information: 0 : C:\Program Files\Microsoft BizTalk ESB Toolkit 2.0\esb.config
    ESBConfigurationTool.exe Information: 0 : The configuration source found was: ESB File Configuration Source
    ESBConfigurationTool.exe Information: 0 : C:\Program Files\Microsoft BizTalk ESB Toolkit 2.0\esb.config
    ESBConfigurationTool.exe Information: 0 : Loaded: Configuration
    ESBConfigurationTool.exe Information: 0 : Executing script: databaseExistsSmoIntegrated.ps1 in view: ExceptionManagementDatabase with parameters: Key: serverInstance Value: AV-BIZTALK-2009, Key: databaseName Value: EsbExceptionDb,
    ESBConfigurationTool.exe Information: 0 : ExceptionManagementDatabase: Configured
    ESBConfigurationTool.exe Information: 0 : The configuration changes were persited to 'ESB File Configuration Source'' from view 'ExceptionManagementDatabase
    ESBConfigurationTool.exe Information: 0 : The configuration source found was: ESB File Configuration Source
    ESBConfigurationTool.exe Information: 0 : C:\Program Files\Microsoft BizTalk ESB Toolkit 2.0\esb.config
    ESBConfigurationTool.exe Information: 0 : The configuration settings were saved to file: C:\Program Files\Microsoft BizTalk ESB Toolkit 2.0\Bin\ESBConfigurationTool.exe.Config
    ESBConfigurationTool.exe Information: 0 : The configuration settings were saved to file: c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Config\machine.config
    ESBConfigurationTool.exe Information: 0 : The machine configuration file for x64 was not found. Path: c:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\Config\machine.config
    ESBConfigurationTool.exe Information: 0 : The configuration changes were persited to 'ESB File Configuration Source'' from view 'Configuration
    ESBConfigurationTool.exe Information: 0 : Executing script: databaseExistsSmoIntegrated.ps1 in view: ExceptionManagementDatabase with parameters: Key: serverInstance Value: AV-BIZTALK-2009, Key: databaseName Value: EsbExceptionDb,
    ESBConfigurationTool.exe Information: 0 : The network path was not found. (Exception from HRESULT: 0x80070035)
    ESBConfigurationTool.exe Error: 0 : An error has occurred:
    The network path was not found. (Exception from HRESULT: 0x80070035)
    Stack Trace:
       at System.DirectoryServices.AccountManagement.UnsafeNativeMethods.IADs.Get(String bstrName)
       at System.DirectoryServices.AccountManagement.CredentialValidator.BindSam(String target, String userName, String password)
       at System.DirectoryServices.AccountManagement.CredentialValidator.Validate(String userName, String password, ContextOptions connectionMethod)
       at System.DirectoryServices.AccountManagement.PrincipalContext.ValidateCredentials(String userName, String password, ContextOptions options)
       at EsbConfigurationTool.Panels.PanelBase.ValidateCredential(NetworkCredential credentials, String groupName)
       at EsbConfigurationTool.Panels.WebServicesException.Save()
       at EsbConfigurationTool.EsbConfiguration.OnTsBtnSaveClick(Object sender, EventArgs e)

    ESBConfigurationTool.exe Information: 0 : The configuration source found was: ESB File Configuration Source
    ESBConfigurationTool.exe Information: 0 : C:\Program Files\Microsoft BizTalk ESB Toolkit 2.0\esb.config
    ESBConfigurationTool.exe Information: 0 : The configuration settings were saved to file: C:\Program Files\Microsoft BizTalk ESB Toolkit 2.0\Bin\ESBConfigurationTool.exe.Config
    ESBConfigurationTool.exe Information: 0 : The configuration settings were saved to file: c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Config\machine.config
    ESBConfigurationTool.exe Information: 0 : The machine configuration file for x64 was not found. Path: c:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\Config\machine.config
    ESBConfigurationTool.exe Information: 0 : The configuration changes were persited to 'ESB File Configuration Source'' from view 'Configuration

     

    • Edited by AnoopVishnoi Monday, October 25, 2010 3:55 PM added details on VPC
    Monday, October 25, 2010 3:48 PM

All replies

  • I seem to remember an issue like this before last year. Google/Bing this newsgroup for this similar issue. In anycase see if this post helps you as well:

    http://social.msdn.microsoft.com/Forums/en-US/biztalkesb/thread/85ccbf11-18a4-488b-a4f1-d1eda450a777 


    MCT, MCSD.NET, BizTalk TS
    Thursday, October 28, 2010 6:13 AM
  • Thanks for the response Dwight, but this even doesn't seem to fit in as I don't have the domain groups/accounts available with me. I am doing this on a Virtual Machine which isn't a part of domain.

     

    --Anoop

    Monday, November 1, 2010 8:27 AM
  • Hi Anoop,

    Is it not that we have to use only Domain Accounts?? This is because when I tried using a Local account on my machine, I got a similar kind of error. Hence, I had to use my domain account. Is there any constraint that you can't use a domain account?? (I don't have idea about VPC, hence the question).

    Regards

    Praveen.


    Praveen Behara
    MCST : BizTalk Server 2006 R2
    Wednesday, November 3, 2010 10:08 AM
  • Check below element in ESBConfigurationTool.exe.config  , if no value try editing config file directly and rerun the config tool. it helped for me!!

    <add key="ExceptionBizTalkIsolatedHostGroup" value="yourdomain \BizTalk Isolated Host Users" />

     

     

     

    Wednesday, November 3, 2010 7:53 PM
  • Hi Praveen,

     

    Thanks for the response. The reason why I can't use DOMAIN account is I'm doing it on a Virtual Machine which unfortunately I cannot bind to the network due to certain restrictions.

     

    --Anoop

    Tuesday, November 9, 2010 10:18 AM
  • I've tried all the solutions/alternates you guys have mentioned ... none works :( ... I'm hoping to get a new VM built and use that one

    Below is the log file data

     

    ESBConfigurationTool.exe Information: 0 : The configuration source found was: ESB File Configuration Source
    ESBConfigurationTool.exe Information: 0 : C:\Program Files\Microsoft BizTalk ESB Toolkit 2.0\esb.config
    ESBConfigurationTool.exe Information: 0 : The configuration settings were saved to file: C:\Program Files\Microsoft BizTalk ESB Toolkit 2.0\Bin\ESBConfigurationTool.exe.Config
    ESBConfigurationTool.exe Information: 0 : The configuration settings were saved to file: c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Config\machine.config
    ESBConfigurationTool.exe Information: 0 : The machine configuration file for x64 was not found. Path: c:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\Config\machine.config
    ESBConfigurationTool.exe Information: 0 : The configuration changes were persited to 'ESB File Configuration Source'' from view 'Configuration
    ESBConfigurationTool.exe Information: 0 : Executing script: databaseExistsSmoIntegrated.ps1 in view: ExceptionManagementDatabase with parameters: Key: serverInstance Value: AV-BIZTALK-2009, Key: databaseName Value: EsbExceptionDb,
    ESBConfigurationTool.exe Information: 0 : The network path was not found. (Exception from HRESULT: 0x80070035)
    ESBConfigurationTool.exe Error: 0 : An error has occurred:
    The network path was not found. (Exception from HRESULT: 0x80070035)
    Stack Trace:
       at System.DirectoryServices.AccountManagement.UnsafeNativeMethods.IADs.Get(String bstrName)
       at System.DirectoryServices.AccountManagement.CredentialValidator.BindSam(String target, String userName, String password)
       at System.DirectoryServices.AccountManagement.CredentialValidator.Validate(String userName, String password, ContextOptions connectionMethod)
       at System.DirectoryServices.AccountManagement.PrincipalContext.ValidateCredentials(String userName, String password, ContextOptions options)
       at EsbConfigurationTool.Panels.PanelBase.ValidateCredential(NetworkCredential credentials, String groupName)
       at EsbConfigurationTool.Panels.WebServicesException.Save()
       at EsbConfigurationTool.EsbConfiguration.OnTsBtnSaveClick(Object sender, EventArgs e)

    ESBConfigurationTool.exe Information: 0 : The configuration source found was: ESB File Configuration Source
    ESBConfigurationTool.exe Information: 0 : C:\Program Files\Microsoft BizTalk ESB Toolkit 2.0\esb.config
    ESBConfigurationTool.exe Information: 0 : The configuration settings were saved to file: C:\Program Files\Microsoft BizTalk ESB Toolkit 2.0\Bin\ESBConfigurationTool.exe.Config
    ESBConfigurationTool.exe Information: 0 : The configuration settings were saved to file: c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Config\machine.config
    ESBConfigurationTool.exe Information: 0 : The machine configuration file for x64 was not found. Path: c:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\Config\machine.config
    ESBConfigurationTool.exe Information: 0 : The configuration changes were persited to 'ESB File Configuration Source'' from view 'Configuration

    --Anoop

    Wednesday, November 10, 2010 9:42 AM
  • Anoop,

    when we say domain acocunt, we moreso mean the format as well. So if you're not in a domain did you try: {ServerName\local-account}

    In otherwords when you're not in a domain, you'd use the name of your server\account.

    Did you try this? I'm also wondering if the "-" dashes in your computer name could be causing an issue. This is a Powershell script that runs and when you use "-" dashes, that's considered a parameter being passed in. especially if it's a space in front of the dash. Just thinking out loud on this one...

     

    Try chaning your server name to one without dashes and reinstall SQL,BizTalk,ESB.

     


    MCT, MCSD.NET, BizTalk TS
    Wednesday, November 10, 2010 6:45 PM
  • oh !! I didn't know about the "-".

    I am following the format for supplying the local user-id

     

     

    I shall change the machine name and let you know.

     

     

     

    --Anoop

    Friday, November 12, 2010 12:43 PM
  • I just ran into the same problem making the same system call to:

    System.DirectoryServices.AccountManagement.UnsafeNativeMethods.IADs.Get
    [ValidatePassword] pc.ValidateCredentials threw System.IO.FileNotFoundException: The network path was not found. (Exception from HRESULT: 0x80070035)

    The problem in my case was the service called by display name "Server" and service name LanmanServer was not running. Starting this service allowed the call to be made successfully.

    Saturday, November 13, 2010 1:19 AM
  • I did check, the lanmanserver service is already running for me. Have also tried changing the name, reinstalling SQL, BizTalk & ESB, still no luck.

     

    --Anoop

     

    Tuesday, November 16, 2010 8:42 AM
  • Hi Anoop,

    Assuming that you are using a 64 bit machine... will not all paths be looking at the Program Files (x86) folder instead of the Program Files folder???

    Or did you get around this issue?

    Regards

    Praveen.


    Praveen Behara
    MCST : BizTalk Server 2006 R2
    Saturday, December 4, 2010 5:39 PM
  • I haven't got a resolution to this issue so far ... I ain't using x64 machine.

     

     

    --anoop

    Monday, December 6, 2010 1:12 PM
  • can you mail me the zipped log at praveenkumar_b@infosys.com.. I would love to have a look at it.

    Regards

    Praveen.


    Praveen Behara
    MCST : BizTalk Server 2006 R2
    Tuesday, December 7, 2010 8:18 PM
  • Finally, on one of the machines running Windows 7, BT 2K10, SQL 2008 R2... we were able to solve it. There are a number of things that we did and one or more might just help others too..

    1. Started the Server service.

    2. Ensured that there are no SQLEXPRESS instances present.

    3. Open SQL Server Configuration Manager. Navigate to SQL Server Network Configuration -> Protocols for MSSQLSERVER. Enable NamedPipes, TCP/IP. Restart the SQL service.

    4. Unconfigured whole ESB.. deleted the EsbExceptionDb and started afresh.

    Viola!!! it is done.


    Praveen Behara
    MCST : BizTalk Server 2006 R2, 2010

    • Proposed as answer by Sajith C P Nair Wednesday, September 11, 2013 6:20 AM
    Thursday, August 8, 2013 11:28 AM
  • Thanks Praveen. Your solution worked for me.

    Regards,

    Sajith C P

    MCTS:BizTalk Server 2006 R2, 2009, 2010

    Wednesday, September 11, 2013 6:22 AM
  • It was the SERVER service that caused the issue in my case. Started working after I start the SERVER service.

    I was pulling my hair to resolve this. 

    Thanks

    Thursday, July 19, 2018 9:32 PM
  • Dash/minus is not an issue, underscore can create problems if you want to be backward compatible

    /Peter

    Friday, July 20, 2018 6:30 AM