I think the "service" version is probably reading a different "Configuration file" to determine authorized clients (IP addresses) and/or users.

The error message seems to come from this code in RPC::PIServer: 

  if (!($result = $self->AcceptUser($user, $password))) {
    $comm->Write($socket,
             [0, "User $user is not permitted to connect."]);
    return 0;
    }

[download]
"AcceptUser" authenticates the username against a user list, which I presume comes from a config file.

Sorry - no time to dig much deeper, but hopefully, this directs you toward solving this issue.

Remember that the SERVICE sees different environment variables (in particular PATH) than running from a cmd shell.

     Syntactic sugar causes cancer of the semicolon.        --Alan Perlis

In reply to Re: Running dbiproxy as a service on Windows by NetWallah
in thread Running dbiproxy as a service on Windows by RandomMonkey

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.