logo elektroda
logo elektroda
X
logo elektroda

[Solved] Migration of the Payer Program database 10.01.001 from sql 2017 express on acces

k45i89o98j66 22479 9
ADVERTISEMENT
Treść została przetłumaczona polish » english Zobacz oryginalną wersję tematu
  • #1 17478929
    k45i89o98j66
    Level 39  
    Migration of the Payer Program database 10.01.001 from sql 2017 express on acces


    Test platform:
    Windows 10 1809 (October) 64bits + all patches.
    Payer program 10.01.001 + all corrections.
    Sql Server Express 2017 64bit + all patches.

    archive file of the payer's database in the .bak format (a copy of the database in SQL Server Express 2017 14.0.1000.169 made at the xyz company does not know anything else) 64bit?

    1. Task to go through migration from sql to accesa database.

    Installing SQL Server Express 2017 approx
    Payer installation approx
    Restoring the database from the xyz.bak file to the sql database ok
    Linking the payer to the sql database approx
    Logging in to the payer about
    Optimization of the base approx

    Migration from 1 sql 2017 to another without any problems.
    However, when migrating from sql to access error as above.
  • ADVERTISEMENT
  • #2 17478970
    Matuzalem
    Level 43  
    It will not be easier to use it 22 560 16 00 * and talk to consultants?

    * Pono from 7 to 18.
  • ADVERTISEMENT
  • #3 17478978
    Prot
    Level 38  
    And you read with help:
    Quote:
    Attention!
    Performing a migration when using a Microsoft SQL Server running under the control of the Windows NT 4.0 operating system requires running the SQL Server service on a user account other than the LOCAL SYSTEM user account (local system). The user on whose account the SQL Server service was started should have the appropriate rights described in this chapter. You can select an account to run the SQL Server service in Microsoft SQL Enterprise Manager or in the properties of the service using the Windows NT administrative tools.
    :?:
  • #4 17478987
    k45i89o98j66
    Level 39  
    22 560 16 00 * I called but nothing specific was able to answer they told me to send meil and wait. and option


    "Attention!
    Performing a migration when using a Microsoft SQL Server running under the control of the Windows NT 4.0 operating system requires running the SQL Server service on a user account other than the LOCAL SYSTEM user account (local system). The user on whose account the SQL Server service was started should have the appropriate rights described in this chapter. You can select an account to run the SQL Server service in Microsoft SQL Enterprise Manager or in the properties of the service using the Windows NT administrative tools.
    :?:


    it was tested but it did not help.
  • ADVERTISEMENT
  • #5 17479149
    Prot
    Level 38  
    However, it is worth reading Payer's help :D
    Quote:
    Attention!
    Because there is no MS JET driver for 64-bit applications, it is not possible to migrate the MS Access database to MS SQL Server or MS SQL Server to MS Access using the 64-bit version of MS SQL Server. To migrate between the base types listed above, use the 32-bit version of MS SQL Server with the MS JET driver for 32-bit applications.
  • #7 17480003
    mieszaczwcz
    Level 31  
    Ask for the certified specialist (you will be the subject, you will learn more) why you have to deal with it yourself are serious matters in case of responsibility is a specialist
  • ADVERTISEMENT
  • #8 17480189
    k45i89o98j66
    Level 39  
    today I received help from the program, I quote:
    "The error is related to the fact that Microsoft has not prepared the appropriate protocol for migration from MS Access to MS SQL for 64-bit servers (and vice versa.) The solution is indirect migration in the Payer program to the MS SQL 32-bit database.

    In case of further problems, in order to analyze the problem in detail, please send the system status from the Płatnik program (Administration - Program settings - System status - Save) and from the screenshot with the error message. "

    the only problem is that the archive is in the .bak format made on the 2017 express server and only on it can be recreated on other versions of sql express 2008 2012 2014 2016 screams with a message about incompatibility of the archive version and can not be restored. On 2017 express without problems are reproduced.

    Added after 20 [minutes]:

    I sent I am waiting for reply.
  • #9 17481672
    k45i89o98j66
    Level 39  
    Migration of the Payer Program database 10.01.001 from sql 2017 express on acces

    Problem solved,
    without technical assistance

    Everything on Windows 10 (1809):
    We install Management Studio 2018 + all update.
    We install SQL Server 2017 Express + all update.
    We install Payer 10.01.001.
    With the help of Management Studio 2018, we restore the database to the server with archivum * .bak.
    We fire the Payer 10.01.001 log in, we connect the sql database to the program, we do
    to optimize the base:
    Start the Payer program and log in as the program administrator.
    From the Administration menu, choose Database Settings.
    The Database Settings window will be displayed on the screen, select Optimize Database from the Base menu.
    The optimization process may take some time, depending on the size of the database. After completing the optimization process, click OK to close the message window.
    We leave the program.
    We go back and update the Payer components.
    We are closing the program.


    We use any program such as * BC ***** t for MS Access and MS SQL or any similar program to export from sql to the accesa file. (completely without the participation of Płatnik i Management Studio 2018).
    We pin the database file to the payer and we enjoy the utility.
  • #10 17481675
    k45i89o98j66
    Level 39  
    Migration of the Payer Program database 10.01.001 from sql 2017 express on acces

    Problem solved,
    without technical assistance

    Everything on Windows 10 (1809):
    We install Management Studio 2018 + all update.
    We install SQL Server 2017 Express + all update.
    We install Payer 10.01.001.
    With the help of Management Studio 2018, we restore the database to the server with archivum * .bak.
    We fire the Payer 10.01.001 log in, we connect the sql database to the program, we do
    to optimize the base:
    Start the Payer program and log in as the program administrator.
    From the Administration menu, choose Database Settings.
    The Database Settings window will be displayed on the screen, select Optimize Database from the Base menu.
    The optimization process may take some time, depending on the size of the database. After completing the optimization process, click OK to close the message window.
    We leave the program.
    We go back and update the Payer components.
    We are closing the program.


    We use any program such as * BC ***** t for MS Access and MS SQL or any similar program to export from sql to the accesa file. (completely without the participation of Płatnik i Management Studio 2018).
    We pin the database file to the payer and we enjoy the utility.

    Added after 1 [minutes]:

    Problem solved,
    without technical assistance

    Everything on Windows 10 (1809):
    We install Management Studio 2018 + all update.
    We install SQL Server 2017 Express + all update.
    We install Payer 10.01.001.
    With the help of Management Studio 2018, we restore the database to the server with archivum * .bak.
    We fire the Payer 10.01.001 log in, we connect the sql database to the program, we do
    to optimize the base:
    Start the Payer program and log in as the program administrator.
    From the Administration menu, choose Database Settings.
    The Database Settings window will be displayed on the screen, select Optimize Database from the Base menu.
    The optimization process may take some time, depending on the size of the database. After completing the optimization process, click OK to close the message window.
    We leave the program.
    We go back and update the Payer components.
    We are closing the program.


    We use any program such as * BC ***** t for MS Access and MS SQL or any similar program to export from sql to the accesa file. (completely without the participation of Płatnik i Management Studio 2018).
    We pin the database file to the payer and we enjoy the utility

Topic summary

The discussion revolves around the migration of the Payer Program database version 10.01.001 from SQL Server 2017 Express to an Access database. Users faced challenges during the migration process, particularly errors when attempting to convert the database format. A key issue identified was the lack of appropriate migration protocols between MS Access and MS SQL for 64-bit servers. Solutions included indirect migration to a 32-bit MS SQL database and using SQL Server Management Studio 2018 for restoring the database from a .bak file. Successful steps involved installing SQL Server 2017 Express, Payer 10.01.001, and optimizing the database settings post-migration.
Summary generated by the language model.
ADVERTISEMENT