The fine people at that number don't know what CentreWare Web is. None of them. Everytime I've called the main number, I have to explain to them what it is and how it's different than the printer web UI at great length for each rep I get passed around to. Eventually they ask one of the engineers or senior reps about it and you'll get passed to a different number that noone answers with a voicemail box that is "not monitored". The only helpful thing on that recording is that they tell you the website to submit a ticket. The website isn't very user friendly at all and takes some guess work to get a ticket submitted. Before we got invested with Xerox products, I'd have assumed that the company would have all of this figured out and streamlined.
From working with GDO support, we were able to resolve the issue with help from SQL Server Management Studio (SSMS - free from MS).
1) Open the database with SSMS
2) Rename the existing Xerox database
3) Right-click the databases folder and restore the database using the .bak file created when backing up with the CWW Utility
4) restart CWW services (2) and restart IIS
Sure wish Xerox would throw some attention/money @ R&D for this product... or at least update the documentation.
I'm running .NET 3.5, .NET 4.7, and the SQL Server 2014 Express that ships with the CWW installer.
Backing up the CWW database works fine.
Restoring the database causes the following error in the event log, and crashes the Configuration Utility.
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IndexOutOfRangeException
at Microsoft.SqlServer.Management.Smo.SqlPropertyMetadataProvider.PropertyNameToIDLookupWithException(System.String, Microsoft.SqlServer.Management.Smo.PropertyAccessPurpose)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
Solved! Go to Solution.