New Question

# Revision history [back]

It may be for sure an issue with the python-windows bindings and load of the requested DLLs.

Are you sure that you're using the latest installer? Can you reproduce the slow behavior by doing as few steps as possible (like reboot, then load - or - uninstalling cloudbase-init, cleaning up the registry/disk remnants, then installing and running the service again)? If yes, then tell us how and/or try replacing for yourself the line above "return" with this:

import importlib
importlib.import_module(parts[0])


To see if the function itself is the problem, but there are many chances that a simple import like:

from cloudbaseinit.osutils.windows import WindowsUtils


will have the same result.

What are the accurate details of your platform (like os name, edition, service pack etc.)?

Also, keep in mind that Microsoft's Windows 2003 support will end in 75 days and ours too, so we can't do too much, especially due to the fac that the installer was tested against Windows Server 2003 x86 SP2 both Enterprise and Standard editions and we couldn't find such noticeable slow situations.

It may be for sure an issue with the python-windows bindings and load of the requested DLLs.

Are you sure that you're using the latest installer? Can you reproduce the slow behavior by doing as few steps as possible (like reboot, then load - or - uninstalling cloudbase-init, cleaning up the registry/disk remnants, then installing and running the service again)? If yes, then tell us how and/or try replacing for yourself the line above "return" with this:

import importlib
module = importlib.import_module(parts[0])


To see if the function itself is the problem, but there are many chances that a simple import like:

from cloudbaseinit.osutils.windows import WindowsUtils


will have the same result.

What are the accurate details of your platform (like os name, edition, service pack etc.)?

Also, keep in mind that Microsoft's Windows 2003 support will end in 75 days and ours too, so we can't do too much, especially due to the fac that the installer was tested against Windows Server 2003 x86 SP2 both Enterprise and Standard editions and we couldn't find such noticeable slow situations.

It may be for sure an issue with the python-windows bindings and load of the requested DLLs.

Are you sure that you're using the latest installer? Can you reproduce the slow behavior by doing as few steps as possible (like reboot, then load - or - uninstalling cloudbase-init, cleaning up the registry/disk remnants, then installing and running the service again)? If yes, then tell us how and/or try replacing for yourself the line above "return" with this:

import importlib
module = importlib.import_module(parts[0])


To see if the function itself is the problem, but there are many chances that a simple import like:

from cloudbaseinit.osutils.windows import WindowsUtils


will have the same result.

result. What are the accurate details of your platform (like os name, edition, service pack etc.)?

Also, keep in mind that Microsoft's Windows 2003 support will end in 75 days and ours too, so we can't do too much, especially due to the fac that the installer was tested against Windows Server 2003 x86 SP2 both Enterprise and Standard editions and we couldn't find such noticeable slow situations.

It may be for sure an issue with the python-windows bindings and load of the requested DLLs.

Are you sure that you're using the latest installer? Can you reproduce the slow behavior by doing as few steps as possible (like reboot, then load - or - uninstalling cloudbase-init, cleaning up the registry/disk remnants, then installing and running the service again)? If yes, then tell us how and/or try replacing for yourself the line above "return" with this:

import importlib
module = importlib.import_module(parts[0])


To see if the function itself is the problem, but there are many chances that a simple import like:

from cloudbaseinit.osutils.windows import WindowsUtils


will have the same result. What are the accurate details of your platform (like os name, edition, service pack etc.)?

Also, keep in mind that Microsoft's Windows 2003 support will end in 75 days and ours too, so we can't do too much, especially due to the fac fact that the installer was tested against Windows Server 2003 x86 SP2 both Enterprise and Standard editions and we couldn't find such noticeable slow situations.