SPIBACKUP AND UPGRADE.docx

SPIBACKUP AND UPGRADE.docx

《SPIBACKUP AND UPGRADE.docx》由会员分享，可在线阅读，更多相关《SPIBACKUP AND UPGRADE.docx（10页珍藏版）》请在冰豆网上搜索。

SPIBACKUPANDUPGRADE

Backup AttemptsGiveODBCErrorforSomeDatabases

AnswerID:

27923  |    Published 10/27/2016   |   Updated 10/30/2016

RelevantProduct（s）

SP_INSTRUMENTATION

Issue

WhenattemptingtocreateaWatcom backup thefollowingerrormessageoccurs:

Failedtoconnecttoadmininthesourcedatabase.999:

SQLSTATE=IM002

[Microsoft][ODBCDriverManager]Datasourcenamenotfoundandnodefaultdriverspecified

ContactIntergraphSupportforfurtherassistance.

Sameworkstationcan backup somedatabases,butnotothers.

Environment

ReportedinVersion:

SP_INSTRUMENTATIONv2013HF7（10.00.00.0256）

Notversionspecific

Resolution

Notedthatthismachinewasableto backup aUSdatabase,butnotfromaChinabasedDB.Whileshowingthatoneworked,andonedidnot,sawthattheversionofMSSQLswitchedfrom2012to2008inthe backup dialogbox.（2k8fortheonethatfails）.

Siteswitchesinifilesbyuseofautility.CheckedtheiniandfoundthatfortheChinadatabases,theDBParmlinespecifiedMSS2008,butforUS,ithadMSS2012.

ManuallyeditedtheChina.inifiletoMSS2012andthe backup started（gotpasttheODBCerror）.

Finalresolutionwastofixthesource.inifilecopiedbytheutility.

Cause

Incorrect.inifilesetting

Badintools.inifilecauses"InconsistencybetweenDatabaseandApplication"messagewiththesameversionnumbers

AnswerID:

21562  |    Published 6/25/2014   |   Updated 2/4/2016

RelevantProduct（s）

SP_INSTRUMENTATION

Issue

UnabletorunSPIduetothefollowingmessage:

InconsistencybetweenDatabaseandApplication

Applicationversion:

09.00.02.0176

Databaseversion:

09.00.02.0176

Environment

Reportedinversion:

SP_Instrumentationv2009SP2（09.00.02.0176）

Notversionspecific.

Resolution

Thismessagecanbecausedbyanintools.inifilethatdoesnothaveproperconnectionparameters.

Replacethecorruptintools.inifileusingoneofthefollowingoptions:

1.Copytheintools.inifromadifferentcomputerthathaspreviouslyconnectedtothesamedomain.

2.CheckDatabasesectionofintools.inifileandensurealltheconnectionparametersareappropriate.Manually makeanyneededcorrections.

3.IfthisistheoriginalSPIclientwheretheintools.iniwascreated,renamethecurrentintools.ini,copyintools.pbz,andrenamethecopytointools.ini.

Ifthisdoesnotresolvetheissue,seeifacorruptc_ver.pbdfileisthecauseasdescribedin Answer22423.

Cause

Theintools.inifiledoesnothaveproperconnectionparameterstoconnecttothecorrectdatabase.

AnSPI backup processwasinterruptedanddidnotfinishsuccessfully.Whentheprocessabortsoriskilled, thedatabaseconnectionparametersinintools.inifilearenotresetasrequired.

InconsistencyBetweenDatabaseandApplication

AnswerID:

31119  |    Published 12/28/2017   |   Updated 12/28/2017

RelevantProduct（s）

SP_INSTRUMENTATION

Issue

Iwasdoinga backup ofmydomainandduringthisprocessAdministrationcrashed.

However,whenItriedtoopenAdministration\SPIagain,igot:

SmartPlantInstrumentation

=======================

InconsistencyBetweenDatabaseandApplication

Applicationversion:

6799424

Databaseversion:

6799426

-------------------------------------------

OK

Ilookedtheintools.iniandIcouldnotfindanythingthatcouldberelatedwiththisissue.

IcheckedtheProjectandLicensetablesandbothshow6799424.

C_ver.pbdalsoshows:

6799424

Environment

Reportedinversion:

SP_INSTRUMENTATIONv2016SP1（11.00.01.0296）.

Notversionspecific.

Resolution

Wefoundunder:

C:

\Users\\AppData\Local\VirtualStore\ProgramFiles（x86）\SmartPlant\Instrumentation

Acopyofintools.iniandc_ver.pbd

Oncewedeletedthemboth,allworkedasitshould.

Cause

Informational.

Backup FailswithNoDefaultDriverError

AnswerID:

27900  |    Published 10/25/2016   |   Updated 10/26/2016

RelevantProduct（s）

SP_INSTRUMENTATION

Issue

AttemptsatrunningSPISybaseSQLAnywhere（Watcom） backups oncertainMS-SQLdomainsfail,whileothersrun,fromthesamephysicalmachine.

Itfailsalmostimmediatelywiththefollowingerror:

Failedtoconnecttoadmininthesourcedatabase.999:

SQLSTATE=IM002

[Microsoft][ODBCDriverManager]Datasourcenamenotfoundandnodefaultdriverspecified

ContactIntergraphSupportforfurtherassistance.

Environment

ReportedinVersion:

SP_INSTRUMENTATIONv2013HF7（10.00.00.0256）

Notversionspecific

Resolution

Tested backup ofsuccessfuldomainandthenswitchedusingacustombatchutilitythatchanged.inifilesandtestedabaddomain.

Notedthatthedatabasesectionofthe backup formstatedthedomainwasMSSQL2012forthegooddomain,andMSSQL2008forthebad.

Onlyoneclientinstalledonmachine.

Reviewofthetwo.inifilesshowedthattheDSNvalueforthebaddomain.inifileswasMSS2008.

Switchedthevaluet