![invalid login in ant migration tool invalid login in ant migration tool](https://www.avenga.com/wp-content/uploads/2020/09/Salesforce-Developer-Experience.jpg)
In this case, request the user to login to the Google Apps account from web and follow the steps listed on this help page for the error 'Web login required': In case you are migrating from GSuite/ Google Apps servers, you may have to log in via the web once to authenticate the IMAP activity in your account.The access to the old server is still in place for the account, until the migration is completed.
#Invalid login in ant migration tool password
- Make sure that the user has not changed the password of the source account when you run the migration.
- One of the basic errors occurs while your previous email account is being authenticated. If there are errors during the migration process, contact BMC Support for assistance.Certain factors need to be checked before you perform migration for users. Each time you run the Migration Tool, a new backup file is created and replaces the previous backup file. The Migration Tool creates a backup of the target database at the configured backup location of the SQL Server. Select a data import option to migrate data.įor more information, see Data import options. The Generate configuration report check box is selected by default. The data configuration dialog box is displayed. The Migration Tool tests the connection and displays a message indicating whether the test is successful.
- For both the source and target login credentials, click Test Connection.
-
Specify the User Name to use for accessing the SQL Server. Specify the Database Name for the target database. Specify the Database Name for the source database. The format of the Server Name is serverName\ instanceName. Specify the SQL Server Name for the target database.
Specify the SQL Server Name for the source database. On the credentials dialog box, specify the login credentials for the source (Track-It! 11.4) and the target (Track-It! 20 xx) databases as follows:įrom the menu, specify the Authentication Type for the source database.įrom the menu, specify the Authentication Type for the target database.
- Select I have read and understood all the information, instructions and limitations. check box, and then click Next.
- On the Welcome screen, review all information about the migration process.
- To run the Migration Tool after its first run, go to the folder where you have installed the Migration Tool and run the DatabaseMigration.exe file. To run the Migration Tool for the first time, perform step 4 of Installing the Migration Tool. This might help in case of errors while migrating assets from BCM.
- We recommend that you take a backup of the BMC Client Management (BCM) database.
- If there are errors during the migration, you can share the backup file created during the migration process with BMC Support for further rectification.
- The source and target information and the backup information are stored in log file named database_information.log.
- The Migration Tool displays a message if the database backup is not successful.
- A backup file is created in the backup folder of the target SQL server (for example, C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Backup\Track-It!- dbName.bak ).
- The following considerations apply to the migration process:
#Invalid login in ant migration tool how to
This topic describes how to use the Migration Tool to migrate your data from Track-It! 11.4 to Track-It! 20 xx.