Migration error from version 1.3.13.0 to 1.6.2.7

Questions about WAPT Server / Requests and help related to the WAPT server
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Locked
filou07
Messages: 18
Registration: December 6, 2018 - 3:33 PM

December 6, 2018 - 3:48 PM

Good morning,

I'm migrating from version 13.13.0 to 1.6.2.7. The post-configuration displays an error when migrating to PostgreSQL because a file appears to be in use. Even after rebooting my server and exiting the WAPT agent, the error persists.

My server is running Windows Server 2012 R2 Datacenter 64-bit

Error text:

Code: Select all

Error during post-config:
System Error, (OS Code 1):
Fonction incorrecte : Traceback (most recent call last):
 File "C:\wapt\\waptserver\upgrade.py", line 189, in 
<module>
comment_mongodb_lines(conf_filename=options.config...
 File "C:\wapt\\waptserver\upgrade.py", line 125, in 
comment_mongodb_lines
  os.rename(conf_filename, '%s.%s' % (conf_filename, 
datetime.datetime.today().strftime(%Y%m%d-%H:%M:...
WindowsError: [Error 32] Le processus ne peut pas acc?der 
au fichier car le fichier est utilis? par un autre processus
Thank you for your help
High
filou07
Messages: 18
Registration: December 6, 2018 - 3:33 PM

December 10, 2018 - 4:50 PM

Is there only one inspired person?

Thank you
High
User avatar
PetApp
Messages: 1
Registration: January 9, 2019 - 10:58
Location: New York

January 9, 2019 - 12:37

filou07 wrote: ↑Dec 6, 2018 - 3:48 PM Good morning,

I'm migrating from version 13.13.0 to 1.6.2.7. The post-configuration displays an error when migrating to PostgreSQL because a file appears to be in use. Even after rebooting my server and exiting the WAPT agent, the error persists.

My server is running Windows Server 2012 R2 Datacenter 64-bit

Error text:

Code: Select all

Error during post-config:
System Error, (OS Code 1):
Fonction incorrecte : Traceback (most recent call last):
 File "C:\wapt\\waptserver\upgrade.py", line 189, in 
<module>
comment_mongodb_lines(conf_filename=options.config...
 File "C:\wapt\\waptserver\upgrade.py", line 125, in 
comment_mongodb_lines
  os.rename(conf_filename, '%s.%s' % (conf_filename, 
datetime.datetime.today().strftime(%Y%m%d-%H:%M:...
WindowsError: [Error 32] Le processus ne peut pas acc?der 
au fichier car le fichier est utilis? par un autre processus
Thank you for your help
I had the same error!
High
User avatar
dcardon
WAPT Expert
Messages: 1932
Registration: June 18, 2014 - 09:58
Location: Saint Sébastien sur Loire
Contact :
Contact dcardon

January 14, 2019 - 8:21 PM

Hello filou07,
filou07 wrote: ↑Dec 6, 2018 - 3:48 PM I'm migrating from version 13.13.0 to 1.6.2.7. The post-configuration displays an error when migrating to PostgreSQL because a file appears to be in use. Even after rebooting my server and exiting the WAPT agent, the error persists.

My server is running Windows Server 2012 R2 Datacenter 64-bit

Error text:

Code: Select all

Error during post-config:
System Error, (OS Code 1):
Fonction incorrecte : Traceback (most recent call last):
 File "C:\wapt\\waptserver\upgrade.py", line 189, in 
<module>
comment_mongodb_lines(conf_filename=options.config...
 File "C:\wapt\\waptserver\upgrade.py", line 125, in 
comment_mongodb_lines
  os.rename(conf_filename, '%s.%s' % (conf_filename, 
datetime.datetime.today().strftime(%Y%m%d-%H:%M:...
WindowsError: [Error 32] Le processus ne peut pas acc?der 
au fichier car le fichier est utilis? par un autre processus
Thank you for your help
It seems your update is failing because the upgrade is blocked due to another process having an exclusive lock on the waptserver.ini file. There's no reason why a process should be blocking this file...

Your problem hasn't inspired many people, so I'll first check your antivirus software. Alternatively, you can install Process Explorer [1] (there's a wapt package available) to see which process has a lock on it.

Sincerely,

Denis

[1] https://docs.microsoft.com/en-us/sysint ... s-explorer
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
High
Amiled1981
Messages: 1
Registration: Nov 12, 2021 - 8:39 p.m.

November 12, 2021 - 8:47 PM

The contrib program pg_upgrade allows an installation to be migrated in-place from one major PostgreSQL version to the next
High
Locked

Return to "WAPT Server"


  • To go further with WAPT