Warning on commit new config - anyone recognise the cause?

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Warning on commit new config - anyone recognise the cause?

L4 Transporter

Folks.

 

I made a rule change this morning - first one in a while (fairly static environment of late) - and when committing, got the following warning

 

Error: Invalid id 6 for os WindowsUWP.(Module: useridd)

 

Anyone recognise this/know the cause/know what I need to do to fix it?

 

Cheers

1 REPLY 1

Community Team Member

Hi,

 

WindowsUWP id 6 is coming from the following section of commit :

 

<global-protect-device minver="6.0.0">
<os>
<entry name="Windows" id="1"/>
<entry name="Mac" id="2"/>
<entry name="iOS" id="3"/>
<entry name="Android" id="4"/>
<entry name="WindowsUWP" id="6"/>
</os>
</global-protect-device>

 

The total numbers of entries in global-protect-device is 5, but the id of WindowsUWP is 6. During the commit, if the id (6) is larger than the total numbers of entries (5), the error will be thrown.

 

The issue seems to be only cosmetic and as far as I can see engineers are working towards a fix already.  If you want to be updated on the fix release then I recommend you open up a case with support.

 

Hope this answers your question.

Cheers !

-Kim. 

 

LIVEcommunity team member, CISSP
Cheers,
Kiwi
Please help out other users and “Accept as Solution” if a post helps solve your problem !

Read more about how and why to accept solutions.
  • 1657 Views
  • 1 replies
  • 0 Likes
  • 101 Subscriptions
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!