Application is crashed after restore from SQL SDP Database
Hello Servicedesk,
we have a Big Problem with SDP6 Build "6012". We have changed at 18.09.2007 the Domainadmin password on all servers. The application SDP is to the time still running without problems. At sunday (22.09.2007) is the database and application crashed. The SDP server is a W2003 system include SP2 and the database is running of a different server (MS SQL 2005). The backup sequenz from SDP6 is daily at 23.00 CET. Our Servicedesk call me with a problem with the SDP6 at 22.09.2007. A restore from the database at monday is not possible. Error code is "Build Number is different, Backup Build is 6000" ?????? . We can not the actual database (SQL 2005) restored. The restore is possible,then crashed the application SDP6. The applcation is normaly runnig with a empty database on MYSQL not MS SQL. The database can normaly read with the SQL tools and MY SQL tools. Who is the problem. Can you help me? The SDP6 is a crictical application in the company.
We have more errors in the WRAPPER.LOG START IS FAILD FROM SERVICEDESK SERVER.
we have a Big Problem with SDP6 Build "6012". We have changed at 18.09.2007 the Domainadmin password on all servers. The application SDP is to the time still running without problems. At sunday (22.09.2007) is the database and application crashed. The SDP server is a W2003 system include SP2 and the database is running of a different server (MS SQL 2005). The backup sequenz from SDP6 is daily at 23.00 CET. Our Servicedesk call me with a problem with the SDP6 at 22.09.2007. A restore from the database at monday is not possible. Error code is "Build Number is different, Backup Build is 6000" ?????? . We can not the actual database (SQL 2005) restored. The restore is possible,then crashed the application SDP6. The applcation is normaly runnig with a empty database on MYSQL not MS SQL. The database can normaly read with the SQL tools and MY SQL tools. Who is the problem. Can you help me? The SDP6 is a crictical application in the company.
We have more errors in the WRAPPER.LOG START IS FAILD FROM SERVICEDESK SERVER.