You can restore missing admin-model database-script information on an affected MDrivenServer when portal push reports an unknown value type; this procedure is for administrators who have access to another server with the same current admin model.
Recognize the problem
This issue can appear as the following error:
Problem in portalpush Unknown valuetype in admin_ECO_ORMAPPING table ()
The known condition is that model information has been cleared from the admin_ECO_ORMAPPING table. The missing information is the database script needed for Evolve in the MDrivenServer Admin database.
Restore the database script from a matching server
Use a second MDrivenServer only when it has the same current admin model as the affected server. Do not use an arbitrary server as the source.
- On the matching source MDrivenServer, open
<mdrivenServer>/admin/EvolveDebugPage.aspx. - Select Get from Current.
- In the Admin DB Script box, copy all resulting XML text.
- On the affected MDrivenServer, open
<mdrivenServer>/admin/EvolveDebugPage.aspx. - Paste the copied XML into the Admin DB Script box.
- Select Submit.
- Select Update Current With Given.
Result: the operation inserts the missing database script into the affected Admin database.
Verify the recovery
After the update, repeat the operation that produced the portal-push error. Confirm that the Unknown valuetype message no longer appears.
If the error remains, confirm that the source server used in the procedure has the same current admin model as the affected server before attempting another update.
Alternative recovery route
The missing script can also be inserted by working directly with the Admin database:
- Download the database.
- Open it with a SQL Compact-capable tool, such as LinqPad.
- Insert the missing database script.
- Upload the model.
Use this route only when you can accurately identify and insert the missing script. The debug-page procedure is the documented recovery path when a matching MDrivenServer is available.