I wanted to create a very simple Partitioning example where all Partitions are on the same FileGroup (to avoid the mess of having a bunch of FileGroups). I used the "ALL" keyword when creating my Scheme.

Given:
CREATE PARTITION SCHEME PS_Foo
   AS PARTITION PFR_Foo_DateTime
  ALL TO ( FG_TestPartitionedLogs ) ; 

CREATE TABLE [dbo].[logging_events]
... ON  PS_Foo(logging_event_timestamp);

Running ManagePartition command results in error
"Create failed for Table 'dbo.logging_events_part2_634076331421614463'.
An exception occurred while executing a Transact-SQL statement or batch. Invalid filegroup 'PS_Foo' specified"
Note that 'PS_Foo' is the Scheme name, not the FileGroup. I'm guessing another case needs to be accounted for that will map the Scheme to the FileGroup when the Scheme uses "ALL".

I expect the problem is a bug in my tool that affects operation when your table contains a long text or long binary column.   I tested you example on a simple table and received no errors.  Can you send me or post the DDL for the original table and I will verify that my upcoming fix will address this situation?

Fixed in version 3.0.