[Solved] NMS - can't create new messages

[Lineapixel]

NMS won't let me create new messages, no matter which template or content I set, it always says "Module Error" on message saving. Nothing more.
It seems I can still edit existing messages.
The only anomaly I found in the "new message" tab is the "return page" dropdown that is blank.
Honestly, I can't exactly say what caused the problem. The website has been up for just 3 months and I succesfully used the NMS module once 2 months ago, then once again just before Christmas, when I found the problem (but in meanwhile occured at least a cmsms update).

I'm running CMSMS 1.11.4, with NMS 2.7 and this module list:

CMSMailer 5.2.1
CMSPrinting 1.0.3
FileManager 1.4.3
MenuManager 1.8.5
MicroTiny 1.2.5
ModuleManager 1.5.5
News 2.12.10
Search 1.7.7
ThemeManager 1.1.7
Captcha 0.4.5
CGExtensions 1.31.3
CGJobMgr 1.2.11
NMS 2.7
FormBuilder 0.7.3
Gallery 1.6
AdvancedContent 0.9.4
JQueryTools 1.1.1
TinyMCE 2.9.12
FrontEndUsers 1.21
CGSimpleSmarty 1.5.2
GoogleMaps 0.2.1
Uploads 1.14.3
DownloadManager 1.5.2

I set up a locale clone website with MAMP for testing a possible solution.
Noone of these action had any result:

• Cleaning Cache
• Repairing Tables
• Overwriting NMS
• Unistalling and reinstalling NMS
• Overwriting CGExtensions (because of template management)
• Running CMSMS upgrade procedure to current version
• Running CMSMS install procedure (keeping all the actual content)

Then I started to uninstall modules to check any compatibility issue, testing NMS' new message procedure after each uninstallation.
I actually have just these basic modules installed

CMSMailer 5.2.1
CMSPrinting 1.0.3
FileManager 1.4.3
MenuManager 1.8.5
ModuleManager 1.5.5
News 2.12.10
Search 1.7.7
ThemeManager 1.1.7
MicroTiny 1.2.5
CGExtensions 1.31.3
CGJobMgr 1.2.11
NMS 2.7

but still the problem persists.

I'm actually pretty lost.
Any help?

[Lineapixel]

After a lot of attempts and a deeper study, I realized the problem was the hierarchical structure of my pages.
In fact the first page, but actually not the default page, was an inactive page.
Sorting the page so the inactive one was not the first in line did nothing, so I supposed it had to be a problem related to the page ID.
Deleting and recreating that page did the trick.

I suppose this may be a bug, and I hope it'll be useful to others.

Cheers.
Chris.