Hi everyone! We're hard at work trying to keep our community clean, so if you see any spam, please report it here and we'll review ASAP!  Thanks a million!
8,819 Users Online
  • 1,696,349 Wallpapers
  • 1,565,068 Members
  • 12,971,712 Votes
  • 5,965,287 Favorites

Anime Fans

This group deals with the awsomeness that anime has to offer and the greatness of anime and how cool it is. Pics of cute,nice,and awsome anime wallpapers are here. If your a fan of anime you should join. become a fan !!!

Group Information

Last Activity: 22 Hours Ago
Group Leader: Souleater27
Moderators: animehtf
Submissions: Open
Group Visitors: 1,858,710
Founded: February 11th, 2013

Top Contributors

Recently Active Members

Recently Joined Members


Resolving the Problematic Sage 50 Pervasive Invalid Date Error

markjames5963 says: 1 Months Ago
One of the more disruptive runtime issues that can suddenly halt processes in Sage 50 Pervasive Invalid Date error (https://sagecontact.com/sage-50-pervasive-invalid-date-error/). Occurring predominantly when generating financial reports or attempting period closing procedures, this error centers around incorrect or conflicting date values passed between Sage 50 and the Pervasive database that houses your backend financial data.

Specifically, the Pervasive Invalid Date error gets triggered when Sage 50 attempts to process a transaction or assemble a report that contains an invalid date or one not conforming to the correct date format settings. Since Pervasive powers the database communicating properly formatted data to Sage 50, any mismatches cause the software processes to fail.

Potential causes leading to invalid dates slipping into the Pervasive database underlying Sage include:

Incorrectly set date formats in Pervasive configuration
Data imports, consolidations or migrations with incorrect regional date settings

Manual date entries in wrong formats
Connectivity drops or errors during date field updates enabling bad values

Rectifying requires carefully checking date formats across databases, importing properly formatted date-driven data only, and potentially Pervasive reconfigurations aligned to Sage 50 standards. Setting the YYYYMMDD format avoids common pitfalls. Permanent solutions however often warrant collaborative troubleshooting with sage 50 support (https://sagecontact.com/) to identify and address root causes.
You must be a member of this group to post replies.
Please first join this group by clicking the bright green button
near the top of the right sidebar, then refresh this page.
This is Desktop Nexus Group, independently organized and operated by members of our community, focused around a specific theme or topic.   Find more groups!
Group Rank