[BUG] paconn is not recognized as the name of a cmdlet

Open
#3,870 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Domain
cli

Research direction

Start with the paconn CLI installation link and reproduce paconn login in the reported PowerShell environment. Collect the missing OS, installation method, CLI version, and shell details; done means paconn is recognized and the login command can run or the failure is documented with a reproducible fix.

Written by the indexing model from the issue text.

Description

bug
Type of Connector

Certified Connector

Name of Connector

PDf4me

Describe the bug

Hi

I had paconn installed on old laptop and i had to switch to new laptop. I have installed using link https://learn.microsoft.com/en-us/connectors/custom-connectors/paconn-cli but it is not working for me. Could someone help me.

Is this a security bug?

No, this is not a security bug

What is the severity of this bug?

Severity 3 - Minor issue

To Reproduce

paconn login
paconn : The term 'paconn' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1

  • paconn login
  •   + CategoryInfo          : ObjectNotFound: (paconn:String) [], CommandNotFoundException
  + FullyQualifiedErrorId : CommandNotFoundException
Expected behavior

paconn should work

Environment summary

Install Method (e.g. pip, interactive script, apt-get, Docker, MSI, edge build)
CLI version (paconn --version)
OS version
Shell Type (e.g. bash, cmd.exe, Bash on Windows)

Additional context

no

Dominant language
C#
Stars
1.3k
Forks
1.5k
Avg merge
5d 15h
Merged PRs (30d)
11

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/PowerPlatformConnectors

All issues in microsoft/PowerPlatformConnectors

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.