Can’t copy application

I would like to copy Datacap application with new name. When I am trying with Datacap Studio, I am getting the error pasted below:

C:DatacapDStudioWpfAppWiz.dll. AssemblyVersion: 9.1.0.0
AssemblyFileVersion: 9.1.0.4.***************** Application Wizard Application Copy Logs *************************
2017-10-06 06:44:38 Source App Directory: \GK-APPDCSOD01VT.tpe.corpDatacapDokumentyLokal
2017-10-06 06:44:38 Source Datacap Directory: \GK-APPDCSOD01VT.tpe.corpDatacap
2017-10-06 06:44:38 Destination Application Folder: C:DatacapDokumentyLokal
2017-10-06 06:44:38 Destination Datacap Folder: C:Datacap
2017-10-06 06:44:38 Reading application data
2017-10-06 06:44:38 Parsing source admin database
2017-10-06 06:44:38 Admin database found: Provider=Microsoft.Jet.OLEDB.4.0;Data Source=\GK-APPDCSOD01VT.tpe.corpDatacapDokumentyLokalDokumentyLokalAdm.mdb;
2017-10-06 06:44:38 Parsing source engine database
2017-10-06 06:44:38 Exception encountered while Parsing source engine database:StartIndex cannot be less than zero.
Parameter name: startIndex
***************** End of Application Wizard Copy Logs *************************

The database string are correct, I tested it in Application Manager. The engine database connection string is: Provider=Microsoft.Jet.OLEDB.4.0;Data Source=C:DatacapDokumentyLokalDokumentyLokalEng.MDB;

I also tried to copy the application with Datacap Application Copy Tool. The application was copied but I can’t configure it in FastDoc. I added a new batch profile, then added new task, chose application, workflow and task profile. After pressing the Save button, the previously selected application automatically changes to base application, from which the new application was copied. Even if I change application name in BatchProfiles.xml, the FastDoc displays another.

So in conclusion both methods failed.

Related:

The Name Registration Response could not be sent due to an error. This error was encountered by the Name Challenge Thread.

Details
Product: Windows Operating System
Event ID: 4187
Source: Wins
Version: 5.0
Component: System Event Log
Symbolic Name: WINS_EVT_CHLSND_REG_RSP_ERR
Message: The Name Registration Response could not be sent due to an error. This error was encountered by the Name Challenge Thread.
   
Explanation

This event record usually indicates a database problem. Additional research will need to be conducted to verify the database problem.

   
User Action

Check Event Viewer and to see if Event ID 4224 is occurring with this event. If it is, the problem is with the database. You might want to try a JETPACK on the database to resolve this problem. If this does not correct the problem, check for database corruption. If the database is corrupted, restore it from the backup.

Related:

An attempt to prepare the storage group ‘%1’ for backup failed because the storage group is already in the process of being backed up. The error code is %2. (Note that if a backup was recently aborted, then it may take several minutes for the system to detect the aborted backup and initiate backup cleanup procedures, so this message may be generated if an attempt was made to backup a storage group before a previous backup attempt had fully terminated.)

Details
Product: Exchange
Event ID: 9840
Source: MSExchangeIS
Version: 8.0
Symbolic Name: msgidSGBackupInProgress
Message: An attempt to prepare the storage group ‘%1’ for backup failed because the storage group is already in the process of being backed up. The error code is %2. (Note that if a backup was recently aborted, then it may take several minutes for the system to detect the aborted backup and initiate backup cleanup procedures, so this message may be generated if an attempt was made to backup a storage group before a previous backup attempt had fully terminated.)
   
Explanation

This Error event indicates that an attempt to perform a backup operation failed. This event occurs when you try to perform a Volume Shadow Copy Service (VSS) backup of a mailbox database or of a public folder database in Microsoft Exchange Server 2007.

This problem may occur if the following conditions are true:

  • VSS uses the Microsoft Jet database engine to freeze or thaw a snapshot backup.

  • The Jet database engine encounters an error.

  • The Jet database engine silently frees all storage groups from the snapshot session when the error occurs.

When these conditions are true, the Jet database engine does not report the correct status of these storage groups to Exchange 2007. Therefore, Exchange 2007 does not reset the backup-in-progress state. If you try to back up the affected storage group again, the symptoms that are described in the “Symptoms” section occur.

   
User Action

To resolve this error, do one or more of the following:

  • Dismount all databases in the storage group. For more information, see How to Dismount a Database.

  • Restart the Microsoft Exchange Information Store service.

For more information, see Microsoft Knowledge Base article 930800, Event ID 9840 is logged when a VSS backup operation fails in Exchange 2007.

If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.

Related:

The Jet database failed to initialize (error %1). Please check the event log for more information.

Details
Product: Windows Operating System
Event ID: 1279
Source: Active Directory
Version: 5.0
Symbolic Name: DIRMSG_INSTALL_FAILED_TO_INIT_JET
Message: The Jet database failed to initialize (error %1). Please check the event log for more information.
   
Explanation

The Active Directory database failed to initialize.

   
User Action

Check the event log for more information.

Related:

Lock request time out period exceeded.

Details
Product: SQL Server
Event ID: 1222
Source: MSSQLServer
Version: 9.00.1281.60
Symbolic Name: LK_TIMEOUT
Message: Lock request time out period exceeded.
   
Explanation

Another transaction held a lock on a required resource longer than this query could wait for it.

   
User Action

Perform the following tasks to alleviate the problem:

  1. Locate the transaction that is holding the lock on the required resource, if possible. Use sys.dm_os_waiting_tasks and sys.dm_tran_locks dynamic management views.

  2. If the transaction is still holding the lock, terminate that transaction if appropriate.

  3. Execute the query again.

If this error occurs frequently change the lock time-out period or modify the offending transactions so that they hold the lock for less time.

Related:

Database “{name}” could not be upgraded to version {number}. Error {error code}.

Details
Product: Exchange
Event ID: 1187
Source: MSExchangeIS
Version: 6.0
Component: Information Store
Symbolic Name: msgidDatabaseUpgradeFailed
Message: Database “{name}” could not be upgraded to version {number}. Error {error code}.
   
Explanation
The database may be out of upgrade sequence or there may be a problem with consistency in the database.
   
User Action
Verify that the version of Exchange that you are using is compatible with the database version.Contact Microsoft Product Support Services for assistance running the Isinteg utility, and then try to upgrade the database again.

Related:

Database resource failure error {error code} occurred in function {name} while accessing the database “{name}”.

Details
Product: Exchange
Event ID: 1160
Source: MSExchangeIS Mailbox Store
Version: 6.0
Component: Information Store
Symbolic Name: msgidJetResourceFailure
Message: Database resource failure error {error code} occurred in function {name} while accessing the database “{name}”.
   
Explanation
This message indicates a disk space error.
   
User Action
Change the server to write its logs to a different drive, or back up the database. If the problem persists, contact Microsoft Product Support Services.

Related: