Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.

If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!

OTTER 3.0 / Fresh install Install with remote DB from InedoHub failed on non-US system



  • Hello
    Just to let you know that Installation of Otter 3.0 from scratch with DB on remote Server failed at the DB step due to wrong account.

    1. You should allow to specify the service account
    2. you should use the SID - S-1-5-2 of "NT Authority\Network service" to grab the "real" name to match for non US system to avoid an error during the setup.
      On french system "NT Authority\Network service" is "AUTORITE NT\RESEAU"
      =======
    ** (unnamed scope) **
     ** (unnamed scope) **
      ** Stop $ServiceName service **
        INFO: Stopping service INEDOOTTERSVC...
        INFO: Service INEDOOTTERSVC does not exist.
    
      ** Stop $WebServiceName service **
        INFO: Stopping service INEDOOTTERWEBSVC...
        INFO: Service INEDOOTTERWEBSVC does not exist.
    
      ** Sleep for 5 seconds **
        INFO: Sleeping for 5 seconds...
        INFO: Done sleeping.
    
      ** Deploy Program Files **
       ** Deploy package to $WorkingDirectory **
        DEBUG: Deploying D:\Otter\Extensions\InedoCore.upack...
       ...
        DEBUG: Deploying D:\Otter\Web\bin\System.ValueTuple.dll...
    
    
      ** Write SQL Connection String to $DbConnectionString **
    
      ** Create Database **
       ** Ensure SQL Database $DbName Exists on <unknown> **
        DEBUG: Attempting to connect to *********\INEDO using Initial Catalog=OTTER3...
        DEBUG: Could not connect using Initial Catalog=OTTER3.
        DEBUG: Executing script: CREATE DATABASE [OTTER3] COLLATE SQL_Latin1_General_CP1_CI_AS...
        DEBUG: Executing script: USE [OTTER3];...
        DEBUG: Executing script: CREATE USER [NT AUTHORITY\NETWORK SERVICE] FOR LOGIN [NT AUTHORITY\NETWORK SERVICE]...
        ERROR: Unhandled exception: System.Data.SqlClient.SqlException (0x80131904): Utilisateur ou groupe Windows NT 'NT AUTHORITY\NETWORK SERVICE' introuvable. Vérifiez une nouvelle fois le nom .....
    Error Number :15401,State :1,Class :16
    
    

    Best regards



  • Hi,

    I succeed to install it.
    The steps I have done:

    • Create Database on the Remote server with correct collation
    • Create file Otter.config in %PROGRAMDATA%\Inedo\SharedConfig
    <?xml version="1.0" encoding="utf-8"?>
    <InedoAppConfig>
      <ConnectionString>Data Source=MYSQLSERVER\MYINSTANCE;Initial Catalog=MYDATABASE;Integrated Security=True</ConnectionString>
      <EncryptionKey>***SOME ENCRYPTION KEY ***</EncryptionKey>
      <WebServer Enabled="false" Urls="http://*:8626/" />
    </InedoAppConfig>
    
    • Create the Inedo Service with the command:
    otter.service.exe install
    

    At this point, nothing is running.

    • Run InedoHub,
      -- Select Uninstall
      this will clean the existing installation
      -- Select Install
      as the DB is already existing, everything is OK

    *In my config, the Otter service have to run with a domain account which owns the Otter DB on the remote server

    During the installation, InedoHub is waiting for the service to start.

    • Go to the Service Manager, change the Service account and start the Service.
    • Change the IIS AppPool with the same account used for the Otter Service

    Et voilà !

    But, if you create the Database before installing Otter, this should make the installation correctly.

    I know it is a little bit messy, I hope this will help if someone meet the same problem


  • inedo-engineer

    Hello;

    We haven't seen this error in quite a long time, and I remember it was something we had addressed ages ago. Internally, we still jokingly call it NT AUTORIDAD from this experience, because who would have guessed they localized those names...

    That said, we didn't really change the installation process for Otter 3.0, and it's really just a copy/paste of the ProGet and BuildMaster installation scripts. I don't know why we wouldn't have heard from it until now.

    It's possible this solution was never brought over to the Inedo Hub? Maybe.. for now, we'd rather not mess with the installation scripts until we get more reports, so we'll just wait to hear more. If anyone else experiences this , in any products, please share it :)

    Alana



  • I had such problem with localized account with a lot of software :)

    Managing the [Otter / Buildmaster / Proget] service Account from the InedoHub would be nice.

    Philippe


Log in to reply
 

Inedo Website HomeSupport HomeCode of ConductForums GuideDocumentation