API-error during assignment

I'm getting an error when using the assignment tool for my host. The following is what I'm running...

C:\Windows\system32>D:\TeamViewer_Assignment.exe -apitoken MY TOKEN -datafile "C:\Program Files (x86)\TeamViewer\AssignmentData.json"

TeamViewer_Assignment (r350)

=> Assignment failed with:
POST-Request 'groups' failed with 500 (API-Error: 'internal_error' (Code 3), Description: 'A group with the same name already exists for this account. Please choose another name.')

Is the code I'm using correct? What does it mean when it same "A group with the same name already exsits for this account"? There is only one group with this name but that's where I want the users to be assigned.

Find more posts tagged with

Accepted answers

edroszcz

Hi,

I got it working by using the -groupID paramter with TeamViewer_Assignment.exe.

You can find the group-id when logging into the Management Console, clicking on the group and checking the URL. At the end of the URL you will find "g/12345678".

Please remove the "/" in order to get your group-id.

For me it looks something like this:

TeamViewer_Assignment.exe -apitoken OURAPITOKEN -datafile "C:\Program Files (x86)\TeamViewer\AssignmentData.json" -devicealias "${COMPUTERNAME}" -allowEasyAccess=true -wait=30 -reassign=true -verbose -groupID "gIDOFGROUP"

All comments

edroszcz

Hi,

I got it working by using the -groupID paramter with TeamViewer_Assignment.exe.

You can find the group-id when logging into the Management Console, clicking on the group and checking the URL. At the end of the URL you will find "g/12345678".

Please remove the "/" in order to get your group-id.

For me it looks something like this:

ABaker

We are receiving the same error.

fultonsheenfan

Same error here! Both Mac and PC assignement fails with the same error code. Group already exists, just adding the computers to the existing group.

Scripts worked fine up to a few days ago.

ABaker

I did call them yesterday and they acknowledged that this is a global issue and they would have it fixed "within a couple of days".

dbartlett

Yes. Adding the g followed by the group number from the management console worked for me.