Avertissement ID 1517

[jawabel]

Bonsoir tt le monde,

 

Voilà, ayant eu ces derniers jours des problèmes répétitifs de plantage de mon pc (svt au moment de quiter windows), relatifs précisément à l'avertissement ID 1517 (service utilisant toujours le Registre pendant la fermeture de la session...et donc mémoire non libérée...), j'ai appliqué la solution proposée par Microsoft dans un tel cas via le lien << http://www.microsoft.com/downloads/details...&DisplayLang=en >>, autrement dit, j'ai téléchargé le service UPHClean dans le but de déterminer le programme qui serait dérrière mon dit problème...Seulement, une fois le téléchargement fait, je n'ai pas su et/ou compris la suite de la solution! Il est vrai qu'un fichier readme.txt est là pour expliquer celà...mais malheureusement je n'y rien pigé ...En fait, d'un côté je suis "bleu" en englais et de l'autre la " traduction mot par mot..désormais" via certains sites spécialisés n'a encore rien donné!

Sur ce, je serais très reconnaissant à celui ou à celle qui pourrait m'apporter une aide là dessus.

 

Merci d'avance et à +,

[Nicolas Coolman]

Bonjour,

 

Peux-tu poster le contenu de ton fichier "readme.txt" ?

[jawabel]

Bonjour coolman et merci pour ta réponse;

 

Voilà ci-dessous le contenu du fichier en question qui est un peu long( j'en suis navré); par ailleurs je vous rappelle que je suis sous XP Pro SP2, Norton antivirus couplé avec ZoneAlarm et Viruskeeper2005...Et si vous avez besoin de quoi que ce soit d'autre, je demeure à votre entière disposition...merci encore :

 

Le fichier readme.txt concerné se présente ainsi:

 

 

UPHClean v1.5e readme.txt

Updated March 4, 2004 by Robin Caron

 

All feedback appreciated to uphclean@microsoft.com

 

WHAT IS UPHCLEAN

================

 

UPHClean is a service that once and for all gets rid of problems with user

profile not unloading.

 

You are having profile unload problems if you experience slow logoff (with

Saving Settings for most of the time while logging off), roaming profiles

that do not reconcile, or the registry size limit is reached.

 

WHY DO PROFILES NOT UNLOAD?

===========================

 

Many system and service processes do work on behalf of users. When the work

is done the system or service process is responsible for releasing handles it

has to the user profile hive. If this is not done by the service as the user

logs off the profile cannot be unloaded.

 

This problem in code can be caused by improper coding either in Microsoft

software or 3rd party software (e.g. printer drivers, virus scanner service,

etc). With the information provided by the system there is no way to find

out what software needs to be corrected to allow profiles to unload.

 

WHAT DOES THE USER SEE? WHAT HAPPENS TO THE PROFILE?

=====================================================

 

Windows NT4:

The system gives up immediately on failure to unload the profile

and the (roaming) profile is not reconciled.

 

Windows 2000:

The system attempts to unload the profile 60 times at 1 second intervals.

This retry logic rarely helps so in most cases after 60 seconds of the user

waiting at the Saving Settings message box the system gives up and roaming

profiles are not reconciled. The number of retries can be changed to allow the

user to log off faster (this can be done using the policy under Computer

Configuration, Administrative Template, System, User Profiles, Maximum retries

to unload and update user profile)

 

Windows XP and 2003:

The profile is reconciled using a copy of the contents of the registry. The

user is not made to wait as in Windows 2000. The problem left is that the

computer cannot recover the memory the profile uses until it can be unloaded.

 

Also in some cases (e.g. using anonymous logons) you may find that you cannot

log on if the profile cannot be unloaded.

 

WHY SHOULD I USE UPHCLEAN?

==========================

 

In the past these issues have been fixed by code changes to release the

registry handle. The disadvantage of this approach is that in many cases

multiple issues (different code paths) are causing the profiles to not

unload. Unless all problem code paths are fixed profiles do not unload.

 

The concept of UPHClean is to deal with these the same way the operating

system deals with other resource issues: when a task is done resources

(memory, handles, etc) are automatically reclaimed. UPHClean accomplishes

this simply by monitoring for users to log off and verifying that unused

resources are reclaimed. If they are not it reclaims the resource and logs

its action. This approach is superior as it works for any known reason

that profiles do not unload and also will keep working to address new

unknown issues.

 

Another advantage to UPHClean is that no computer restart is required to

install it or remove it (except on Windows NT 4). You can install and

remove UPHClean to find out whether it helps with a profile unload problem or

not. You can do this without having to worry about what hotfix, service pack,

feature pack, etc has been installed. Set it and forget is the goal of

UPHClean.

 

By default UPHClean takes action to allow profiles to unload. You can

choose to have UPHClean only report what processes it finds preventing profiles

from unloading. To do this, install UPHClean and use the registry editor to

set:

 

HKLM\System\CurrentControlSet\Services\UPHClean\Parameters\REPORT_ONLY to 1.

 

You can also have UPHClean log the call stack that is responsible for the

profile hive handle. This is necessary to find out what software is

responsible for the hive handle in processes used for many purposes (e.g.

svchost.exe, dllhost.exe, winmgmt.exe). To enable call stack logging use the

registry editor to set:

 

HKLM\System\CurrentControlSet\Services\UPHClean\Parameters\CALLSTACK_LOG to 1.

 

Logging the call stack is computationally and memory intensive. You should use

this option to collect information and then turn it off. To get more accurate

call stack logging it may be necessary to get symbols installed on the

computer. You can read about getting symbols at:

 

http://www.microsoft.com/whdc/ddk/debugging/symbols.mspx

 

HOW CAN I TELL IF I'M HAVING A PROFILE UNLOAD PROBLEM?

======================================================

 

Events are recorded in the event log in most cases. You can use Event Viewer

to look for the following events:

 

Windows NT 4:

 

The application event log has error events with source Userenv, event id

1000. The event text is:

 

The operating system was unable to load your profile. Please contact

your Network Administrator.

 

This is the only symptom you find in the event log of a Windows NT 4 computer

indicating this problem is present. The only way to be sure is to use UPHClean

to find out if you have this problem or have some other problem.

 

Windows 2000:

 

The application event log has error events with source Userenv, event id

1000. When you call up the event you get the one of following events:

 

Windows cannot unload your registry file. If you have a roaming profile,

your settings are not replicated. Contact your administrator.

 

DETAIL - Access is denied.

 

- or -

 

Windows cannot unload your registry class file. If you have a roaming

profile, your settings are not replicated. Contact your administrator.

 

DETAIL Access is denied.

 

- or -

 

Windows cannot log you on because the profile cannot be loaded. Contact

your network administrator.

 

This last error is relevant if you find one of the other ones earlier

in the application log.

 

Windows XP and 2003:

 

You will see of the following error events in the application log:

 

Userenv/1517:

 

Windows saved user X registry while an application or service was still

using the registry during log off. The memory used by the user's registry

has not been freed. The registry will be unloaded when it is no longer in use.

 

This is often caused by services running as a user account, try configuring the

services to run in either the LocalService or NetworkService account.

 

Userenv/1524:

 

Windows cannot unload your classes registry file - it is still in use by other

applications or services. The file will be unloaded when it is no longer in use.

 

Userenv/1500:

 

Windows cannot log you on because your profile cannot be loaded. Check that you

are connected to the network, or that your network is functioning correctly. If

this problem persists, contact your network administrator.

 

This last error (1500) is relevant if you find one of the other ones earlier in

the application log.

 

INSTALLATION

============

 

To automatically install it (you need uphclean-setup.msi):

- Double click the setup.msi

 

To manually install it (you need a copy of uphclean.exe):

 

- Create a directory under Program Files for the service

(e.g. c:\program files\uphclean)

- Copy the program (uphclean.exe) to the directory

(e.g. c:\program files\uphclean\uphclean.exe)

- Open a command prompt on the computer

- Change directory where you copied the program

(e.g cd \program files\uphclean)

- Run the program with the -install switch to install the service and start it

(e.g. uphclean -install)

 

The service is set to automatically start when the computer boots so you will

not need to start it manually. Below I've listed the events that you will find

in the application log when it takes positive steps to unload profile hives.

 

INSTALLATION PROBLEMS

=====================

 

If you get an error using the MSI installation package and the package is on a

network share attempt the installation from a local drive. Another alternative

is to use the manual installation instructions.

 

If you have problems with the installation check to see if the following DLLs

are in your c:\winnt\system32 directory:

 

msvcp60.dll

msvcrt.dll

 

These files are commonly on computers because of other installed software.

If you are missing these files you can visit:

 

http://support.microsoft.com/default.aspx?scid=259403

 

to download vcredist.exe which includes these files.

 

On Windows NT4 you will need to restart the computer. On restart UPHClean will

start automatically.

 

UPGRADING

=========

 

If you used the manual installation method to install UPHClean you must follow

the manual removal instructions before attempting to use the MSI package to

install. You can find out if you used the MSI package by looking for an entry

for User Profile Hive Cleanup Service in Add/Remove Programs under Control Panel.

 

If you used the MSI package to install then you can proceed with the new package

without removal.

 

REMOVAL

=======

 

If you used automatic installation:

- Open Control Panel

- Open Add/Remove Programs

- Click on User Profile Hive Service and select Remove

 

 

If you manually installed:

- Run the program with the -remove switch to stop the service and remove it (e.g. uphclean -remove)

- Remove the UPHClean directory under c:\program files

 

LOGGED EVENTS

=============

 

1) Every time the User Profile Hive Cleanup service starts:

 

Event Type: Information

Event Source: UPHClean

Event Category: None

Event ID: 1001

Date: 11/14/2003

Time: 10:13:45 PM

User: N/A

Computer: RCARONDOM-DC1

Description:

User Profile Hive Cleanup Service version 1.5.0.8 started successfully.

 

2) Every time it stops:

 

Event Type: Information

Event Source: UPHClean

Event Category: None

Event ID: 1010

Date: 7/11/2003

Time: 11:12:06 PM

User: N/A

Computer: RCARONDOM-DC1

Description:

User Profile Hive Cleanup Service stopped successfully.

 

3) Here the service is telling you that it closed handles that were preventing

the profile from unloading:

 

Event Type: Information

Event Source: UPHClean

Event Category: None

Event ID: 1201

Date: 11/14/2003

Time: 10:26:29 PM

User: RCARONDOM\u1

Computer: RCARONDOM-DC1

Description:

The following handles in user profile hive RCARONDOM\u1

(S-1-5-21-3230802392-3390281410-1560515013-1307) have been closed because they were preventing the profile from unloading successfully:

 

profleak.exe (1444)

HKCU (0x144)

 

If you have call stack logging the event will look like this:

 

Event Type: Information

Event Source: UPHClean

Event Category: None

Event ID: 1201

Date: 10/21/2003

Time: 5:17:38 PM

User: RCARONDOM-DC1\u1

Computer: RCARONDOM-DC1

Description:

The following handles in user profile hive RCARONDOM-DC1\u1

(S-1-5-21-3230802392-3390281410-1560515013-1307) have been closed because they were preventing the profile from unloading successfully:

 

profleak.exe (2604)

HKCU (0x80)

0x77dfc200 ADVAPI32!TrackObject+0xe

0x00412112 profleak!<no symbol>

0x77db571b ADVAPI32!ScSvcctrlThreadA+0xe

HKCU\Software\Policies (0x88)

0x77dfc200 ADVAPI32!TrackObject+0xe

0x77da1949 ADVAPI32!RegOpenKeyExW+0x10b

0x0041350c profleak!<no symbol>

0x00412112 profleak!<no symbol>

0x77db571b ADVAPI32!ScSvcctrlThreadA+0xe

 

4) Here's what it looks like if there's a problem closing handle held by

application. I don't expect that will happen.

 

Event Type: Information

Event Source: UPHClean

Event Category: None

Event ID: 1211

Date: 7/11/2003

Time: 9:46:29 PM

User: RCARONDOM\u1

Computer: RCARONDOM-DC1

Description:

The following handles opened in user profile hive RCARONDOM\u1

(S-1-5-21-3230802392-3390281410-1560515013-1307) could not be closed:

 

profleak.exe (1148)

HKCU\SOFTWARE\Policies (0xb0) error 6

 

5) Here the service is telling you that the user profile hive could not be

unloaded and that it will try again later. I expect that this will occur

if the 1211 event occurred. As I don't expect 1211 to occur I'd expect that

event id 1111 will not occur either.

 

Event Type: Warning

Event Source: UPHClean

Event Category: None

Event ID: 1111

Date: 7/11/2003

Time: 9:46:50 PM

User: RCARONDOM\u1

Computer: RCARONDOM-DC1

Description:

User profile hive RCARONDOM\u1 (S-1-5-21-3230802392-3390281410-1560515013-1307)

failed to unload. The unload will be retried.

 

6) If you are using the reporting only mode (see above on how to set) you will

get event id 1501 whenever UPHClean detects a user logging off and the profile

being held:

 

Event Type: Information

Event Source: uphclean

Event Category: None

Event ID: 1501

Date: 7/11/2003

Time: 11:19:49 PM

User: RCARONDOM\u1

Computer: RCARONDOM-DC1

Description:

The following handles opened in user profile hive RCARONDOM\u1

(S-1-5-21-3230802392-3390281410-1560515013-1307) are preventing profiles from unloading:

 

profleak.exe (1364)

HKCU\SOFTWARE\Policies (0xb4)

HKCU (0xb8)

 

7) If you are using the reporting only mode (see above on how to set) you will

get event id 1511 whenever UPHClean detects a hive loaded for an extended

period of time if the user is not logged on (whether there are handles

to it or not). This is important because it is possible that terminal

server could run out of kernel mode resource (paged pool memory) when that

happens. This could lead to users being prevented from logging on.

 

Event Type: Information

Event Source: UPHClean

Event Category: None

Event ID: 1511

Date: 10/21/2003

Time: 5:13:18 PM

User: RCARONDOM\u1

Computer: RCARONDOM

Description:

User profile hive RCARONDOM\u1 (S-1-5-21-3230802392-3390281410-1560515013-1307)

is loaded even though user is not logged on.

 

UPHCLEAN HISTORY

================

 

Mar 4, 2004 v1.5e (build 1.5.4.21)

 

Added code to handle closure of handles for registry keys that were deleted.

This covers scenarios where an application keeps a handle to a deleted

registry key. In that case Userenv would log profile unload problem events

even if UPHClean was running.

 

Feb 25, 2004 v1.5d (build 1.5.4.20)

 

Added code to force closure of registry handles protected from close. This

avoids repeated events 1201 with the same process/handle combinations at 10

second intervals. Modified code to avoid license violation error on NT4.

 

Feb 12, 2004 v1.5c (build 1.5.0.18)

 

Cleaned up event 1201 message text. Added code to delay initial scan for

profiles until operating system has been started for 1 minute. Added logging

code for event id 1501 to include user name. First version available through

Microsoft download.

 

Jan 14, 2004 v1.5b (build 1.5.0.11)

 

Improved detection of profile hive unload problem to allow UPHClean to release

hive handles earlier than before allowing normal system function. With this

change the UPHClean 1201 event will be the only event logged.

 

Jan 5, 2004 v1.5 (build 1.5.0.

 

Added code to allow the call stack to be logged. Modified code to handle

scenario where UPHClean would not clean up profile handles if the profile is

deleted at log off.

 

Sep 23, 2003 v1.2 (build 1.2.0.7)

 

Modified code to allow it to run on Windows NT 4. Also added code to allow

UPHClean to be used in monitoring mode. In this mode UPHClean reports what

process had handles to registry keys in user profile hives. The name of the

process, its id, the registry key name reported.

 

Sep 8, 2003 v1.1 (build 1.1.0.4)

 

Modified code flow to allow UPHClean to work on computers that do not have

terminal services. Modified code to immediately close handles to profile hives

upon detection of user logoff. The user can log off 20 seconds faster that way.

 

Jul 31, 2003 v1.0 (build 1.0.0.2)

 

First working version.

 

WORK FLOW

=========

 

hivestatus: hive name, prior refcount, refcount

hivetounload: hive name, next attempt (60 seconds)

pendinghiveunload: hive name, next attempt (10 seconds), last attempt (60 mins)

handletoclose: handle info

 

wait until computer has been up for 1 minute

 

on profile list change notify or service done or timeout (10 seconds if !pendinghiveunload.empty else 60 seconds)

if service done -- exit

 

iterate through hive status:

prior refcount = refcount

update refcount

if refcount = 0 and loaded then

if prior refcount != 0 then

remove hive from hivetounload

add hive to pendinghiveunload

(next attempt = now, last attempt = now + 65 mins)

else

remove hive from hivetounload

remove hive from pendinghiveunload

 

iterate through pendinghiveunload

if last attempt passed then

move hive to hivetounload (next attempt = now)

 

if !pendinghiveunload.empty or !hivetounload.empty then

handletoclose = null

get handlelist

iterate through handlelist

if (start(handle.name) in pendinghiveunload and nextattempt <= now) or

(start(handle.name) in hivetounload and nextattempt <= now) then

add entry to handletoclose

 

process handletoclose (all handles on list are to be closed)

 

process hivetounload (hives with nextattempt <= now should be unloaded)

no need to remove from list (will get done at next hive status update)

 

 

Fin du texte

[Nicolas Coolman]

Salut,

 

Le partie intéressante est celle-ci :

INSTALLATION

============

 

To automatically install it (you need uphclean-setup.msi):

- Double click the setup.msi

 

To manually install it (you need a copy of uphclean.exe):

 

- Create a directory under Program Files for the service

(e.g. c:\program files\uphclean)

- Copy the program (uphclean.exe) to the directory

(e.g. c:\program files\uphclean\uphclean.exe)

- Open a command prompt on the computer

- Change directory where you copied the program

(e.g cd \program files\uphclean)

- Run the program with the -install switch to install the service and start it

(e.g. uphclean -install)

 

The service is set to automatically start when the computer boots so you will

not need to start it manually. Below I've listed the events that you will find

in the application log when it takes positive steps to unload profile hives.

 

L'installation se fait automatiquement en double cliquant sur le fichier setup.msi.

 

Si tu as un message d'erreur, reposte !

 

A+

[jawabel]

Re, et merci pour ton assistance,

 

Voilà, je tiens à vous rappeler que le téléchargement et l'installation du programme en question ne m'ont pas posé problème...Par contre c'est ce qui vient après...que je n'ai pas compris; autrement dit que dois-je faire après pour résoudre le fond du problème?

 

a+,

[Nicolas Coolman]

Si je comprends bien,

Tu as appliqué la méthode Microsoft en installant le fichier msi, que cette installation s'est faite correctement, mais que tu as toujours le même message d'erreur qui s'affiche sur le userenv 1517 ?

[jawabel]

Salut coolman,

 

Oui c'est ça : j'ai téléchargé et installé le programme UPHClean de chez microsoft, mais je crois comprendre qu'on me demande d'effectuer d'autres applications supplémentaires dans le but que ledit programme puisse me permettre d'identifier rapidement le service local de mon système qui serait dérrière le problème de plantage auquel je me trouve confronté de temps à autre ( juste après le demarrage de windows et non avant la fermeture de windows comme je l'ai signalé auparavant par erreur ).

Voilà, et donc je vous signale que le problème est tj présent du moment que je n'ai pas encore achevé la solution...En fait c'est parce que comme je vous l'ai dit je ne comprend rien à l'anglais..

 

p.s: Je signale toutefois que j'ai pu m' apercevoir de la présence du nouveau service (ou programme) au niveau de l'observatoire d'evennements ( applications) sans pour autant savoir comment en tirer profit. En double cliquant sur l'information qui le concerne je n'apprend rien d'autre à part : " Le service(UPHClean) a demarré avec succés".

 

Voilà tout, A +;

 

Cordialement,

 

jawabel

[jawabel]

Salut coolman,

 

Oui c'est ça : j'ai téléchargé et installé le programme UPHClean de chez microsoft, mais je crois comprendre qu'on me demande d'effectuer d'autres applications supplémentaires dans le but que ledit programme puisse me permettre d'identifier rapidement le service local de mon système qui serait dérrière le problème de plantage auquel je me trouve confronté de temps à autre ( juste après le demarrage de windows et non avant la fermeture de windows comme je l'ai signalé auparavant par erreur ).

Voilà, et donc je vous signale que le problème est tj présent du moment que je n'ai pas encore achevé la solution...En fait c'est parce que comme je vous l'ai dit je ne comprend rien à l'anglais..

 

p.s: Je signale toutefois que j'ai pu m' apercevoir de la présence du nouveau service (ou programme) au niveau de l'observatoire d'evennements ( applications) sans pour autant savoir comment en tirer profit. En double cliquant sur l'information qui le concerne je n'apprend rien d'autre à part : " Le service(UPHClean) a demarré avec succés".

 

Voilà tout, A +;

 

Cordialement,

 

jawabel

[Nicolas Coolman]

C'est dèjà plus clair

 

Ce problème a été référencé sur "hotline-pc.org"

 

- Résoudre un problème au moment de la fermeture du compte d'utilisateur :

Un utilitaire proposé par Microsoft vous permet de résoudre un problème de déconnexion. Sous Windows XP, ce type d'erreur est consignée dans l'Observateur d'événements dans le menu Applications. En voici les principales indications :

* Source : Userenv - ID évén. : 1517 ou 1524 : le Registre est utilisé par un service ou une application empêchant le déchargement de la ruche utilisateur.

* Source : Userenv - ID évén. : 1500 : Windows ne peut pas vous connecter à votre compte car le profil est introuvable ou endommagé.

Le descriptif de l'erreur peut être celui-ci : Windows a sauvegardé le Registre utilisateur alors qu'une application ou un service utilisait toujours le Registre pendant la fermeture de la session. La mémoire employée par le Registre de l'utilisateur n'a pas été libérée. Le Registre sera déchargé lorsqu'il ne sera plus utilisé. Les symptômes sont les suivants : l'ordinateur reste longtemps sur la page Enregistrement de vos paramètres, ou votre profil utilisateur n'est pas enregistré. Téléchargez à cette adresse : www.microsoft.com/downloads/details.aspx?familyid=1B286E6D-8912-4E18-B570-42470E2F3582&displaylang=en ces trois fichiers : UPHClean-Setup.msi, uphclean.exe et readme.txt. Double-cliquez sur le fichier .msi afin d'installer le programme. Vous pourrez le désinstaller par le module Ajout/Suppression de programmes du Panneau de configuration. Le principe est assez simple : ce programme se charge en tant que service.

UPHClean empêche simplement qu'aucune ressource inutile soit appelée quand le Registre utilisateur est sauvegardé. Vous pouvez limiter ce programme pour qu'il vous affiche seulement un rapport d'erreur indiquant quel processus empêche la déconnexion automatique.

1) Cliquez sur Démarrer/Exécuter, puis saisissez : regedit.

2) Dans le Registre, ouvrez HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\UPHClean\Parameters.

3) Éditez une valeur DWORD nommée REPORT_ONLY.

4) Affectez-lui comme données de la valeur le chiffre 1.

Les rapports qui seront générés seront visibles dans l'Observateur d'événements.

 

Voilà ce que dit le site de a.Vouillon

 

Avertissements ID 1517 et 1524 dans le journal Application de l'Observateur d'évènement:

ID 1517:"Windows a sauvegardé le Registre utilisateur ... alors qu'une application ou un service utilisait toujours le Registre pendant la fermeture de la session. La mémoire utilisée par le Registre de l'utilisateur n'a pas été libérée. le Registre sera déchargé lorsqu'il ne sera plus utilisé.

Cela est souvent causé par des services s'exécutant en tant que compte d'utilisateur, essayez de configurer les services pour s'exécuter dans le compte service réseau ou service local."

ID 1524: "Windows ne peut pas décharger vos classes fichier de Registre - il est en cours d'utilisation par d'autres applications ou services. Le fichier sera déchargé quand il ne sera plus utilisé."

 

==> Microsoft a développé User Profile Hive Cleanup Service qui se charge de fermer les applications qui maintiennent des ruches du registre ouverte. Il logue aussi le nom des application et les clés du registre responsables, ce qui peut permettre la résolution du problème.

D'autres solutions ou suggestions moins courantes sont également proposées sur le site: WINDOWS XPSHUTDOWN & RESTART dont sont tirées certaines des pistes ci-dessus.

[jawabel]

Re-bonsoir coolman,

 

Alors si je comprends bien, il n'ya rien à ajouter d'autre à l'installation de uphclean pour voir la solution à mon problème aboutir? (si le problème est celui là et qu'il n'ya rien d'autre de plus bien evidemment !)...ok, mais quand je pense à cette longueur du fichier readme.txt qui lui est associé!...A mon sens, je me dis que s'il s'agissait uniquement d'apporter la solution à ce niveau, on aurait pu le dire en "quatre mots"! non?...Bref, peu importe Mr coolman, même si mon problème demeure tj là, j'espère le résoudre incessament grâce à ce formidable forum qu'est Zebulon...Et déjà jusque là, je peux dire que vous n'avez epargné aucun effort pour venir à mon aide, et donc je vous en remercie infiniment en conséquence.

 

Bonne nuit et à +,

 

Amicalement jawabel;