Your entire ERP system is essential to your success, and Sage Software's ClientCare Support Plans provide you with the technical expertise you need to keep your accounting system running smoothly. Sage offers five annual ClientCare Support Plans that are designed with your most-frequently requested service options in mind. All Sage MAS 90 and Sage MAS 200 products require a maintenance or support program for the first year.
When you invested in Sage MAS ERP software, you implemented a powerful, convenient set of solutions that expand as your business grows. Customers on a Maintenance plan will receive unlimited access to our Knowledge base via Sage Software Online. Phone support is available to purchase with this plan on a per-case basis. Plus plans include unlimited access to selected Sage MAS 90 and Sage MAS 200 Anytime Learning courses. Maximize your Sage investment with a Maintenance or Maintenance Plus Plan.
The Silver Support Plan is for the Sage MAS 90 and 200 customer who requires interaction with our support team. You'll get unlimited expert telephone support through a toll-free number. Plus plans include unlimited access to selected Sage MAS 90 and Sage MAS 200 Anytime Learning courses.
If you place heavy demands on your Sage MAS 90 or 200 ERP system and require priority support, the Gold Support Plan is for you. It provides unlimited telephone support, unlimited access to selected Sage MAS 90 and Sage MAS 200 Anytime Learning courses, and access to a dedicated toll-free number.
To renew your Client Care service plan, call 1-866-709-2432 or order online today.
Error Diagnostics Info
---------------------------------------------------------------
Could not contact the Search Server
Error Trace Info
---------------------------------------------------------------
at Plumtree.Remote.PRC.Search.SearchRequestWrapper.Execute()
at Sage.CMS.Foundation.Data.Document.GetDocuments(Gateway Gateway, Int32 RootFolderID, Boolean SearchSubFolders, String[] FieldsToReturn, String FieldToSortBy, Boolean SortAscending, SearchPropertyCondition[] SearchPropertyConditions)
at Sage.CMS.Foundation.Data.Document.GetDocuments(Gateway Gateway, Int32 RootFolderID, Boolean SearchSubFolders, SearchPropertyCondition[] SearchPropertyConditions)
at Sage.CMS.Foundation.Data.Document.GetDocuments(Gateway Gateway, Int32 RootFolderID, SearchPropertyCondition[] SearchPropertyConditions)
at Sage.CMS.Portlets.ActionItems.ActionItems.Page_Load(Object sender, EventArgs e)
An error has occured on the portal
---------------------------------------------------------------
Date/Time of Occurrence: 3/18/2010 9:05:57 AM
Server: portletscms.gs.adinternal.com
Environment: .com
Page causing the error: C:\webcms\internal\SagePortlets\Sage.CMS\Sage.CMS.Portlets.ActionItems\v2.0\webapp\ActionItems.aspx
Client IP Address: 10.11.96.64
Browser being used: CCBot/1.0 (+http://www.commoncrawl.org/bot.html)
Referring Page:
Logon User:
Query String:
Requested Method: GET
Server Protocol: HTTP/1.1
Server Software: Microsoft-IIS/6.0
Machine Name: NAATLWEBPTRL3
Portal Gateway Information
---------------------------------------------------------------
Portlet: Sage.CMS.Portlets.ActionItems
Community: http://www.sagemas.com/support_services/mas90_mas200
Sub Portal: http://www.sagemas.com
Cookie Struct Variables
---------------------------------------------------------------
Session Struct Variables
---------------------------------------------------------------
Form Variables
---------------------------------------------------------------
QueryString Variables
---------------------------------------------------------------
Could not contact the Search Server
Server Error in '/SAGE.CMS.PORTLETS/ACTIONITEMS' Application.
Could not contact the Search Server
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: Plumtree.Remote.PRC.Search.SearchException: Could not contact the Search Server
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.