FBA Generic Command Behaviour

[Prakash437]

Hi all,

I repost this message because the reply to my last post seems to have been
not noticed ..

Anyway here is my reply once again..

Are you sure you set FBA phases to something > 9000?

Yes, the phases are infact 9000 and 9100!!

From your FBA log it seems that the phases were set somewhere between 2100

and 4500:

Well, that's what is my question ?? why does it execute it at this
phase,
when it is supposed to do it only after 9000 (which anyway it does.)

******************** 2100 phase *****************************
16:51:57 PM - [CallEntryPointThread] C:\WINDOWS\system32\odbcconf.dll,
DllRegisterServer
******************** Your FBA commands *****************************
16:52:03 PM - [FBALaunch] C:\WINDOWS\system32\msiexec.exe /regserver

(ExitCode: 0x0)

This is a system related FBA command. Its not my FBA command !! I
highlighted it here to relate it to the one that follows, which is of
our interest.

16:52:34 PM - [FBALaunch] C:\WINDOWS\system32\msiexec.exe /i

"C:\WINDOWS\system32\WMEncoder.msi" /qn (ExitCode: 0x641)

This is my Command. It is being executed now (and fails) and again
after all
system specific FBA commands are done (and succeeds). (Note: i have not
shown that part of the FBA Log file).

******************** 4500 phase *****************************
16:52:41 PM - [FBALaunch] C:\WINDOWS\system32\lodctr.exe

/c:C:\WINDOWS\system32\perfd009.dat /h:C:\WINDOWS\system32\perfi009.dat

/l:009 (ExitCode: 0x0)

If acceptable, you may want to attach your SLD here so that we could

take a look at it.

I uploaded the SLD at this location, please check it.

http://www.geocities.com/prakash437/installer.zip

Thanks for your reply,
Prakash

 

[KM]

Prakash437,

Something is not working with your access to the NG. You missed the reply, although it is perfectly seen from here.

Anyway, here was my reply below.... (basically I asked you to provide your System Hive for review)

-------------------------

I replied to your response yesterday. Today i am surprised to see that
the message is not yet posted on the group ..

Nope, did not see you reply here.
Sometimes public newsgroup servers behave weird :-(

Yes, the phases are infact 9000 and 9100!!

I just saw your component. The phase are indeed the ones you set.

Well, that's what is my question ?? why does it execute it at this
phase, when it is supposed to do it only after 9000 (which anyway it does.)

Seems that your component's FBA generic command(s) phases get reset to 4500.
My very rough guess would be that this may happen because you have the "Windows Installer Service" specified in the dependency list.
The "Windows Installer Service" installs the msiexec service at the 4500 FBA system phase (that is the FBA command just before your
own FBA command you saw in the log file).

Why your phases are getting reset - I don't have a clue.

I can't build your component here as I don't have your repository.

Would you mind send us (through the website) the "system" hive of the built (pre-FBA) image? I want to take a look at the FBA
commands set up there.

--

KM,
BSquare Corp.

PS. A while ago we have created the componentized version of the WMEcoder. If you are interested, contact BSquare for more details.

Prakash437,

Are you sure you set FBA phases to something > 9000?

From your FBA log it seems that the phases were set somewhere between 2100 and 4500:


******************** 2100 phase *****************************
16:51:57 PM - [CallEntryPointThread]

C:\WINDOWS\system32\odbcconf.dll, DllRegisterServer

******************** Your FBA commands *****************************
16:52:03 PM - [FBALaunch] C:\WINDOWS\system32\msiexec.exe /regserver (ExitCode: 0x0)
16:52:34 PM - [FBALaunch] C:\WINDOWS\system32\msiexec.exe /i

"C:\WINDOWS\system32\WMEncoder.msi" /qn (ExitCode: 0x641)

******************** 4500 phase *****************************
16:52:41 PM - [FBALaunch] C:\WINDOWS\system32\lodctr.exe

/c:C:\WINDOWS\system32\perfd009.dat /h:C:\WINDOWS\system32\perfi009.dat

/l:009 (ExitCode: 0x0)



If acceptable, you may want to attach your SLD here so that we could take a look at it.

--
Regards,
KM, BSquare Corp.

Hello everyone,
I have 2 FBA generic commands, one executing an application installer, and
the later deleting the installer file. Their phases are 9000 and 9100
respectively.

Ofcourse, these commands are executed and i get the desired
result. And out of curiosity when i checked the FBA log i find that one of
the Generic command is executed, way too early (infact a few minutes into
the FBA) and exits with an exit code:0x641. The installer actually uses the
services of msiexec.exe. Here i provide that little part of FBA log, which i
feel is fishy??

FYI, the same command is again executed finally successfully and exits with
the code: 0x00.

Any ideas if there is anything wrong in it ?? Or is it some sort of
initializing ?? if yes why only this generic command, when i have other
commands aswell.

Monday, January 31, 2005

16:49:08 PM - [FBASetProgressText] Setting PNP Flag...
16:49:55 PM - [FBAApplySecurityStringToRegKey] RegSetKeySecurity Failed!
Error: 0x6
16:49:56 PM - [FBAReplaceSecurityInRegistry]
FBAApplySecurityStringToRegKey(009) #1 Failed!
16:50:07 PM - [FBASetProgressText] Initializing...
16:50:08 PM - [CallEntryPointThread] C:\WINDOWS\FBA\FBALIB.DLL,
FBAInitialize
16:50:08 PM - [FBASetProgressText] Setting SystemPrefix...
16:50:09 PM - [FBASetProductKey] Evaluation product key
16:50:10 PM - [FBASetProgressText] Initializing User Profiles...
16:50:22 PM - [CallEntryPointThread] C:\WINDOWS\FBA\FBALIB.DLL, FBAStep1
16:50:23 PM - [CallEntryPointThread] C:\WINDOWS\FBA\FBALIB.DLL,
FBASetSetupInfo
16:50:24 PM - [FBASetProgressText] Installing System Security...
16:51:43 PM - [FBAInstallSecurity] Successfully set security!
16:51:45 PM - [CallEntryPointThread] C:\WINDOWS\FBA\FBASEC.DLL,
FBAInstallSecurityPhase1
16:51:45 PM - [FBASetProgressText] Registering Components...
16:51:46 PM - [CallEntryPointThread] C:\WINDOWS\system32\atl.dll,
DllRegisterServer
16:51:48 PM - [CallEntryPointThread] C:\WINDOWS\system32\txflog.dll,
DllRegisterServer
16:51:49 PM - [CallEntryPointThread] C:\WINDOWS\system32\netcfgx.dll,
DllRegisterServer
16:51:51 PM - [CallEntryPointThread] C:\WINDOWS\system32\netman.dll,
DllRegisterServer
16:51:53 PM - [CallEntryPointThread] C:\WINDOWS\system32\netshell.dll,
DllRegisterServer
16:51:57 PM - [CallEntryPointThread] C:\WINDOWS\system32\odbcconf.dll,
DllRegisterServer

************************************** Note these lines
***********************************************************
16:52:03 PM - [FBALaunch] C:\WINDOWS\system32\msiexec.exe /regserver
(ExitCode: 0x0)
16:52:34 PM - [FBALaunch] C:\WINDOWS\system32\msiexec.exe /i
"C:\WINDOWS\system32\WMEncoder.msi" /qn (ExitCode: 0x641)
************************************** Note these lines
***********************************************************

16:52:41 PM - [FBALaunch] C:\WINDOWS\system32\lodctr.exe
/c:C:\WINDOWS\system32\perfd009.dat /h:C:\WINDOWS\system32\perfi009.dat
/l:009 (ExitCode: 0x0)
16:52:42 PM - [CallEntryPointThread] C:\WINDOWS\system32\MSCTF.dll,
DllRegisterServer
16:52:44 PM - [CallEntryPointThread] C:\WINDOWS\system32\rsaenh.dll,
DllRegisterServer
16:52:46 PM - [CallEntryPointThread] C:\WINDOWS\system32\dssenh.dll,
DllRegisterServer

Thanks,
prakash

 

[Prakash437]

Hope you can see this post ..

Anyway here is the system hive ..
http://www.geocities.com/prakash437/SYSTEM.zip

Can you tell me how can we read these files ..

And one more thing: The phases are not being over written. The FBA command
at 9000 still remains, but somehow a copy of it is being made with its phase
set to 4500.

Thanks for your reply.

Prakash

PS. A while ago we have created the componentized version of the WMEcoder.
If you are interested, contact BSquare for more details.

I dont think this to be free .. isnt it?

Prakash437,

Something is not working with your access to the NG. You missed the reply,

although it is perfectly seen from here.

Anyway, here was my reply below.... (basically I asked you to provide your System Hive for review)

-------------------------


Nope, did not see you reply here.
Sometimes public newsgroup servers behave weird :-(


I just saw your component. The phase are indeed the ones you set.
does.)

Seems that your component's FBA generic command(s) phases get reset to 4500.
My very rough guess would be that this may happen because you have the

"Windows Installer Service" specified in the dependency list.

The "Windows Installer Service" installs the msiexec service at the 4500

FBA system phase (that is the FBA command just before your

own FBA command you saw in the log file).

Why your phases are getting reset - I don't have a clue.

I can't build your component here as I don't have your repository.

Would you mind send us (through the website) the "system" hive of the

built (pre-FBA) image? I want to take a look at the FBA

commands set up there.

--

KM,
BSquare Corp.

PS. A while ago we have created the componentized version of the WMEcoder.

If you are interested, contact BSquare for more details.

Prakash437,

Are you sure you set FBA phases to something > 9000?

From your FBA log it seems that the phases were set somewhere between 2100 and 4500:


******************** 2100 phase *****************************
16:51:57 PM - [CallEntryPointThread]

C:\WINDOWS\system32\odbcconf.dll, DllRegisterServer

******************** Your FBA commands *****************************
16:52:03 PM - [FBALaunch] C:\WINDOWS\system32\msiexec.exe /regserver (ExitCode: 0x0)
16:52:34 PM - [FBALaunch] C:\WINDOWS\system32\msiexec.exe /i

"C:\WINDOWS\system32\WMEncoder.msi" /qn (ExitCode: 0x641)

******************** 4500 phase *****************************
16:52:41 PM - [FBALaunch] C:\WINDOWS\system32\lodctr.exe

/c:C:\WINDOWS\system32\perfd009.dat /h:C:\WINDOWS\system32\perfi009.dat

/l:009 (ExitCode: 0x0)



If acceptable, you may want to attach your SLD here so that we could take a look at it.

--
Regards,
KM, BSquare Corp.


Hello everyone,
I have 2 FBA generic commands, one executing an application installer, and
the later deleting the installer file. Their phases are 9000 and 9100
respectively.

Ofcourse, these commands are executed and i get the desired
result. And out of curiosity when i checked the FBA log i find that one of
the Generic command is executed, way too early (infact a few minutes into
the FBA) and exits with an exit code:0x641. The installer actually uses the
services of msiexec.exe. Here i provide that little part of FBA log, which i
feel is fishy??

FYI, the same command is again executed finally successfully and exits with
the code: 0x00.

Any ideas if there is anything wrong in it ?? Or is it some sort of
initializing ?? if yes why only this generic command, when i have other
commands aswell.

Monday, January 31, 2005

16:49:08 PM - [FBASetProgressText] Setting PNP Flag...
16:49:55 PM - [FBAApplySecurityStringToRegKey] RegSetKeySecurity Failed!
Error: 0x6
16:49:56 PM - [FBAReplaceSecurityInRegistry]
FBAApplySecurityStringToRegKey(009) #1 Failed!
16:50:07 PM - [FBASetProgressText] Initializing...
16:50:08 PM - [CallEntryPointThread] C:\WINDOWS\FBA\FBALIB.DLL,
FBAInitialize
16:50:08 PM - [FBASetProgressText] Setting SystemPrefix...
16:50:09 PM - [FBASetProductKey] Evaluation product key
16:50:10 PM - [FBASetProgressText] Initializing User Profiles...
16:50:22 PM - [CallEntryPointThread] C:\WINDOWS\FBA\FBALIB.DLL, FBAStep1
16:50:23 PM - [CallEntryPointThread] C:\WINDOWS\FBA\FBALIB.DLL,
FBASetSetupInfo
16:50:24 PM - [FBASetProgressText] Installing System Security...
16:51:43 PM - [FBAInstallSecurity] Successfully set security!
16:51:45 PM - [CallEntryPointThread] C:\WINDOWS\FBA\FBASEC.DLL,
FBAInstallSecurityPhase1
16:51:45 PM - [FBASetProgressText] Registering Components...
16:51:46 PM - [CallEntryPointThread] C:\WINDOWS\system32\atl.dll,
DllRegisterServer
16:51:48 PM - [CallEntryPointThread] C:\WINDOWS\system32\txflog.dll,
DllRegisterServer
16:51:49 PM - [CallEntryPointThread] C:\WINDOWS\system32\netcfgx.dll,
DllRegisterServer
16:51:51 PM - [CallEntryPointThread] C:\WINDOWS\system32\netman.dll,
DllRegisterServer
16:51:53 PM - [CallEntryPointThread] C:\WINDOWS\system32\netshell.dll,
DllRegisterServer
16:51:57 PM - [CallEntryPointThread] C:\WINDOWS\system32\odbcconf.dll,
DllRegisterServer

************************************** Note these lines
***********************************************************
16:52:03 PM - [FBALaunch] C:\WINDOWS\system32\msiexec.exe /regserver
(ExitCode: 0x0)
16:52:34 PM - [FBALaunch] C:\WINDOWS\system32\msiexec.exe /i
"C:\WINDOWS\system32\WMEncoder.msi" /qn (ExitCode: 0x641)
************************************** Note these lines
***********************************************************

16:52:41 PM - [FBALaunch] C:\WINDOWS\system32\lodctr.exe
/c:C:\WINDOWS\system32\perfd009.dat /h:C:\WINDOWS\system32\perfi009.dat
/l:009 (ExitCode: 0x0)
16:52:42 PM - [CallEntryPointThread] C:\WINDOWS\system32\MSCTF.dll,
DllRegisterServer
16:52:44 PM - [CallEntryPointThread] C:\WINDOWS\system32\rsaenh.dll,
DllRegisterServer
16:52:46 PM - [CallEntryPointThread] C:\WINDOWS\system32\dssenh.dll,
DllRegisterServer

Thanks,
prakash

 

[KM]

Prakash437,

Hope you can see this post ..

I do!

Anyway here is the system hive ..
http://www.geocities.com/prakash437/SYSTEM.zip

Can you tell me how can we read these files ..

You can just load it with regedit (File menu --> Load Hive Option).

However, something wrong with the file you sent. I had to do a lot of security changes in order to view it.
Do you build it on to a NTFS folder? Does the folder have any NTFS secutiry permission set?

And one more thing: The phases are not being over written. The FBA command
at 9000 still remains, but somehow a copy of it is being made with its phase set to 4500.

I checked the set up FBA commands on your build. They all seem to be set up properly. You have only one command with 9000 phase
number set.
I don't have a clue why it gets duplicated at run time.

Could you share out your entire FBALog once again?

KM

Thanks for your reply.

Prakash

PS. A while ago we have created the componentized version of the WMEcoder.
If you are interested, contact BSquare for more details.

I dont think this to be free .. isnt it?

Prakash437,

Something is not working with your access to the NG. You missed the reply,

although it is perfectly seen from here.

Anyway, here was my reply below.... (basically I asked you to provide your System Hive for review)

-------------------------


Nope, did not see you reply here.
Sometimes public newsgroup servers behave weird :-(


I just saw your component. The phase are indeed the ones you set.
does.)

Seems that your component's FBA generic command(s) phases get reset to 4500.
My very rough guess would be that this may happen because you have the

"Windows Installer Service" specified in the dependency list.

The "Windows Installer Service" installs the msiexec service at the 4500

FBA system phase (that is the FBA command just before your

own FBA command you saw in the log file).

Why your phases are getting reset - I don't have a clue.

I can't build your component here as I don't have your repository.

Would you mind send us (through the website) the "system" hive of the

built (pre-FBA) image? I want to take a look at the FBA

commands set up there.

--

KM,
BSquare Corp.

PS. A while ago we have created the componentized version of the WMEcoder.

If you are interested, contact BSquare for more details.

KM wrote:
Prakash437,

Are you sure you set FBA phases to something > 9000?

From your FBA log it seems that the phases were set somewhere between
2100 and 4500:


******************** 2100 phase *****************************
16:51:57 PM - [CallEntryPointThread]
C:\WINDOWS\system32\odbcconf.dll, DllRegisterServer


******************** Your FBA commands *****************************
16:52:03 PM - [FBALaunch] C:\WINDOWS\system32\msiexec.exe /regserver
(ExitCode: 0x0)
16:52:34 PM - [FBALaunch] C:\WINDOWS\system32\msiexec.exe /i
"C:\WINDOWS\system32\WMEncoder.msi" /qn (ExitCode: 0x641)

******************** 4500 phase *****************************
16:52:41 PM - [FBALaunch] C:\WINDOWS\system32\lodctr.exe
/c:C:\WINDOWS\system32\perfd009.dat /h:C:\WINDOWS\system32\perfi009.dat
/l:009 (ExitCode: 0x0)



If acceptable, you may want to attach your SLD here so that we could
take a look at it.

--
Regards,
KM, BSquare Corp.


Hello everyone,
I have 2 FBA generic commands, one executing an application
installer, and
the later deleting the installer file. Their phases are 9000 and
9100
respectively.

Ofcourse, these commands are executed and i get the desired
result. And out of curiosity when i checked the FBA log i find that
one of
the Generic command is executed, way too early (infact a few
minutes into
the FBA) and exits with an exit code:0x641. The installer actually
uses the
services of msiexec.exe. Here i provide that little part of FBA
log, which i
feel is fishy??

FYI, the same command is again executed finally successfully and
exits with
the code: 0x00.

Any ideas if there is anything wrong in it ?? Or is it some sort of
initializing ?? if yes why only this generic command, when i have
other
commands aswell.

Monday, January 31, 2005

16:49:08 PM - [FBASetProgressText] Setting PNP Flag...
16:49:55 PM - [FBAApplySecurityStringToRegKey] RegSetKeySecurity
Failed!
Error: 0x6
16:49:56 PM - [FBAReplaceSecurityInRegistry]
FBAApplySecurityStringToRegKey(009) #1 Failed!
16:50:07 PM - [FBASetProgressText] Initializing...
16:50:08 PM - [CallEntryPointThread] C:\WINDOWS\FBA\FBALIB.DLL,
FBAInitialize
16:50:08 PM - [FBASetProgressText] Setting SystemPrefix...
16:50:09 PM - [FBASetProductKey] Evaluation product key
16:50:10 PM - [FBASetProgressText] Initializing User Profiles...
16:50:22 PM - [CallEntryPointThread] C:\WINDOWS\FBA\FBALIB.DLL,
FBAStep1
16:50:23 PM - [CallEntryPointThread] C:\WINDOWS\FBA\FBALIB.DLL,
FBASetSetupInfo
16:50:24 PM - [FBASetProgressText] Installing System Security...
16:51:43 PM - [FBAInstallSecurity] Successfully set security!
16:51:45 PM - [CallEntryPointThread] C:\WINDOWS\FBA\FBASEC.DLL,
FBAInstallSecurityPhase1
16:51:45 PM - [FBASetProgressText] Registering Components...
16:51:46 PM - [CallEntryPointThread] C:\WINDOWS\system32\atl.dll,
DllRegisterServer
16:51:48 PM - [CallEntryPointThread]
C:\WINDOWS\system32\txflog.dll,
DllRegisterServer
16:51:49 PM - [CallEntryPointThread]
C:\WINDOWS\system32\netcfgx.dll,
DllRegisterServer
16:51:51 PM - [CallEntryPointThread]
C:\WINDOWS\system32\netman.dll,
DllRegisterServer
16:51:53 PM - [CallEntryPointThread]
C:\WINDOWS\system32\netshell.dll,
DllRegisterServer
16:51:57 PM - [CallEntryPointThread]
C:\WINDOWS\system32\odbcconf.dll,
DllRegisterServer

************************************** Note these lines
***********************************************************
16:52:03 PM - [FBALaunch] C:\WINDOWS\system32\msiexec.exe
/regserver
(ExitCode: 0x0)
16:52:34 PM - [FBALaunch] C:\WINDOWS\system32\msiexec.exe /i
"C:\WINDOWS\system32\WMEncoder.msi" /qn (ExitCode: 0x641)
************************************** Note these lines
***********************************************************

16:52:41 PM - [FBALaunch] C:\WINDOWS\system32\lodctr.exe
/c:C:\WINDOWS\system32\perfd009.dat
/h:C:\WINDOWS\system32\perfi009.dat
/l:009 (ExitCode: 0x0)
16:52:42 PM - [CallEntryPointThread]
C:\WINDOWS\system32\MSCTF.dll,
DllRegisterServer
16:52:44 PM - [CallEntryPointThread]
C:\WINDOWS\system32\rsaenh.dll,
DllRegisterServer
16:52:46 PM - [CallEntryPointThread]
C:\WINDOWS\system32\dssenh.dll,
DllRegisterServer

Thanks,
prakash

 

[Prakash437]

KM,

Do you build it on to a NTFS folder?

yes ..

Does the folder have any NTFS secutiry permission set?
well the entire drive is shared .. and the drive is indexed .. maybe these
has any effect

Could you share out your entire FBALog once again? www.geocities.com/prakash437/FBALOG.zip

Regards,
Prakash

KM

Thanks for your reply.

Prakash

PS. A while ago we have created the componentized version of the WMEcoder.
If you are interested, contact BSquare for more details.

I dont think this to be free .. isnt it?

Prakash437,

Something is not working with your access to the NG. You missed the

reply,
although it is perfectly seen from here.

Anyway, here was my reply below.... (basically I asked you to provide

your
System Hive for review)

-------------------------

I replied to your response yesterday. Today i am surprised to see that
the message is not yet posted on the group ..

Nope, did not see you reply here.
Sometimes public newsgroup servers behave weird :-(

Yes, the phases are infact 9000 and 9100!!

I just saw your component. The phase are indeed the ones you set.

Well, that's what is my question ?? why does it execute it at this
phase, when it is supposed to do it only after 9000 (which anyway it does.)

Seems that your component's FBA generic command(s) phases get reset to 4500.
My very rough guess would be that this may happen because you have the

"Windows Installer Service" specified in the dependency list.

The "Windows Installer Service" installs the msiexec service at the

4500
FBA system phase (that is the FBA command just before your

own FBA command you saw in the log file).

Why your phases are getting reset - I don't have a clue.

I can't build your component here as I don't have your repository.

Would you mind send us (through the website) the "system" hive of the

built (pre-FBA) image? I want to take a look at the FBA

commands set up there.

--

KM,
BSquare Corp.

PS. A while ago we have created the componentized version of the

WMEcoder.
If you are interested, contact BSquare for more details.

KM wrote:
Prakash437,

Are you sure you set FBA phases to something > 9000?

From your FBA log it seems that the phases were set somewhere between
2100 and 4500:


******************** 2100 phase *****************************
16:51:57 PM - [CallEntryPointThread]
C:\WINDOWS\system32\odbcconf.dll, DllRegisterServer


******************** Your FBA commands *****************************
16:52:03 PM - [FBALaunch] C:\WINDOWS\system32\msiexec.exe /regserver
(ExitCode: 0x0)
16:52:34 PM - [FBALaunch] C:\WINDOWS\system32\msiexec.exe /i
"C:\WINDOWS\system32\WMEncoder.msi" /qn (ExitCode: 0x641)

******************** 4500 phase *****************************
16:52:41 PM - [FBALaunch] C:\WINDOWS\system32\lodctr.exe
/c:C:\WINDOWS\system32\perfd009.dat /h:C:\WINDOWS\system32\perfi009.dat
/l:009 (ExitCode: 0x0)



If acceptable, you may want to attach your SLD here so that we could
take a look at it.

--
Regards,
KM, BSquare Corp.


Hello everyone,
I have 2 FBA generic commands, one executing an application
installer, and
the later deleting the installer file. Their phases are 9000 and
9100
respectively.

Ofcourse, these commands are executed and i get the desired
result. And out of curiosity when i checked the FBA log i find that
one of
the Generic command is executed, way too early (infact a few
minutes into
the FBA) and exits with an exit code:0x641. The installer actually
uses the
services of msiexec.exe. Here i provide that little part of FBA
log, which i
feel is fishy??

FYI, the same command is again executed finally successfully and
exits with
the code: 0x00.

Any ideas if there is anything wrong in it ?? Or is it some sort of
initializing ?? if yes why only this generic command, when i have
other
commands aswell.

Monday, January 31, 2005

16:49:08 PM - [FBASetProgressText] Setting PNP Flag...
16:49:55 PM - [FBAApplySecurityStringToRegKey] RegSetKeySecurity
Failed!
Error: 0x6
16:49:56 PM - [FBAReplaceSecurityInRegistry]
FBAApplySecurityStringToRegKey(009) #1 Failed!
16:50:07 PM - [FBASetProgressText] Initializing...
16:50:08 PM - [CallEntryPointThread] C:\WINDOWS\FBA\FBALIB.DLL,
FBAInitialize
16:50:08 PM - [FBASetProgressText] Setting SystemPrefix...
16:50:09 PM - [FBASetProductKey] Evaluation product key
16:50:10 PM - [FBASetProgressText] Initializing User Profiles...
16:50:22 PM - [CallEntryPointThread] C:\WINDOWS\FBA\FBALIB.DLL,
FBAStep1
16:50:23 PM - [CallEntryPointThread] C:\WINDOWS\FBA\FBALIB.DLL,
FBASetSetupInfo
16:50:24 PM - [FBASetProgressText] Installing System Security...
16:51:43 PM - [FBAInstallSecurity] Successfully set security!
16:51:45 PM - [CallEntryPointThread] C:\WINDOWS\FBA\FBASEC.DLL,
FBAInstallSecurityPhase1
16:51:45 PM - [FBASetProgressText] Registering Components...
16:51:46 PM - [CallEntryPointThread] C:\WINDOWS\system32\atl.dll,
DllRegisterServer
16:51:48 PM - [CallEntryPointThread]
C:\WINDOWS\system32\txflog.dll,
DllRegisterServer
16:51:49 PM - [CallEntryPointThread]
C:\WINDOWS\system32\netcfgx.dll,
DllRegisterServer
16:51:51 PM - [CallEntryPointThread]
C:\WINDOWS\system32\netman.dll,
DllRegisterServer
16:51:53 PM - [CallEntryPointThread]
C:\WINDOWS\system32\netshell.dll,
DllRegisterServer
16:51:57 PM - [CallEntryPointThread]
C:\WINDOWS\system32\odbcconf.dll,
DllRegisterServer

************************************** Note these lines
***********************************************************
16:52:03 PM - [FBALaunch] C:\WINDOWS\system32\msiexec.exe
/regserver
(ExitCode: 0x0)
16:52:34 PM - [FBALaunch] C:\WINDOWS\system32\msiexec.exe /i
"C:\WINDOWS\system32\WMEncoder.msi" /qn (ExitCode: 0x641)
************************************** Note these lines
***********************************************************

16:52:41 PM - [FBALaunch] C:\WINDOWS\system32\lodctr.exe
/c:C:\WINDOWS\system32\perfd009.dat
/h:C:\WINDOWS\system32\perfi009.dat
/l:009 (ExitCode: 0x0)
16:52:42 PM - [CallEntryPointThread]
C:\WINDOWS\system32\MSCTF.dll,
DllRegisterServer
16:52:44 PM - [CallEntryPointThread]
C:\WINDOWS\system32\rsaenh.dll,
DllRegisterServer
16:52:46 PM - [CallEntryPointThread]
C:\WINDOWS\system32\dssenh.dll,
DllRegisterServer

Thanks,
prakash

 

[Slobodan Brcin \(eMVP\)]

Hi,

I guess that I do not see root of this thread, but I assume that this is what you are talking about:
17:39:56 PM - [FBALaunch] C:\WINDOWS\system32\msiexec.exe /i "C:\WINDOWS\system32\WMEncoder.msi" /qn (ExitCode: 0x641)
18:21:51 PM - [FBALaunch] C:\WINDOWS\system32\msiexec.exe /i "C:\WINDOWS\system32\WMEncoder.msi" /qn (ExitCode: 0x0)

I have also loaded system. hive but without any errors in process. (I'm using regedit that is started from the service in the system
account and this allow me to bypass problems that Konstantin reported.)
Based on system. hive WMEncoder should be executed only once. This is really most unusual.

Probably stupid question but here it go anyway: Are you sure that you have used send us FBA.log from the same image that you send us
registry hive?

BTW: Is it ok that FBA takes more than an hour?

Regards,
Slobodan

 

[Prakash437]

HI,

I guess that I do not see root of this thread, but I assume that this is what you are talking about:
17:39:56 PM - [FBALaunch] C:\WINDOWS\system32\msiexec.exe /i

"C:\WINDOWS\system32\WMEncoder.msi" /qn (ExitCode: 0x641)

18:21:51 PM - [FBALaunch] C:\WINDOWS\system32\msiexec.exe /i

"C:\WINDOWS\system32\WMEncoder.msi" /qn (ExitCode: 0x0)

Yes, this is what we were talking abt ..

I have also loaded system. hive but without any errors in process. (I'm

using regedit that is started from the service in the system

account and this allow me to bypass problems that Konstantin reported.)
Based on system. hive WMEncoder should be executed only once. This is

really most unusual.

Can you try to build an image of your own with this component .. See if you
see the same behaviour ..
Component: www.geocities.com/prakash437/installer.zip

Probably stupid question but here it go anyway: Are you sure that you have

used send us FBA.log from the same image that you send us

registry hive?

Yes. Its the same one.

BTW: Is it ok that FBA takes more than an hour?

This is one more worrying factor to me .. Its a EWF protected image on a CF
card. But what makes me *not* complain is that the run-time image works
exactly as i wish. Everything is perfectly installed. Also, its response has
been considerably slow when i try copying image from my Windows XP
development machine. it takes well over, 10 minutes to copy an image of
230MB. Isnt this normal for a CF card ?? If not i guess this has something
to do with the CF-IDE adapter ..

Regards,
Prakash

 

[KM]

Prakash437,

I actually did similar to what Slobodan did - ran the regedit in Local System context and this was easier to load your System hive.
Another trick was to change the hive and all its subkeys owner in security permissions.
What's bothering me is that I have never had to do that with any System hive build with TD. THis tells me something is wrong on your
dev machine.

Anyway, look at the first few lines of the FBALog. You will notice:
17:36:30 PM - [FBASetProgressText] Setting PNP Flag...
17:37:19 PM - [FBAApplySecurityStringToRegKey] RegSetKeySecurity Failed! Error: 0x6
17:37:19 PM - [FBAReplaceSecurityInRegistry] FBAApplySecurityStringToRegKey(009) #1 Failed!

I still believe something is wrong with your build. Particulary, could you check NTFS Security permission set on the build directory
for this image?
(drive indexing should not have anything to do with it)

KM

HI,

I guess that I do not see root of this thread, but I assume that this is what you are talking about:
17:39:56 PM - [FBALaunch] C:\WINDOWS\system32\msiexec.exe /i

"C:\WINDOWS\system32\WMEncoder.msi" /qn (ExitCode: 0x641)

18:21:51 PM - [FBALaunch] C:\WINDOWS\system32\msiexec.exe /i

"C:\WINDOWS\system32\WMEncoder.msi" /qn (ExitCode: 0x0)

Yes, this is what we were talking abt ..

I have also loaded system. hive but without any errors in process. (I'm

using regedit that is started from the service in the system

account and this allow me to bypass problems that Konstantin reported.)
Based on system. hive WMEncoder should be executed only once. This is

really most unusual.

Can you try to build an image of your own with this component .. See if you
see the same behaviour ..
Component: www.geocities.com/prakash437/installer.zip

Probably stupid question but here it go anyway: Are you sure that you have

used send us FBA.log from the same image that you send us

registry hive?

Yes. Its the same one.

BTW: Is it ok that FBA takes more than an hour?

This is one more worrying factor to me .. Its a EWF protected image on a CF
card. But what makes me *not* complain is that the run-time image works
exactly as i wish. Everything is perfectly installed. Also, its response has
been considerably slow when i try copying image from my Windows XP
development machine. it takes well over, 10 minutes to copy an image of
230MB. Isnt this normal for a CF card ?? If not i guess this has something
to do with the CF-IDE adapter ..

Regards,
Prakash

 

[KM]

Prakash437,

PS. A while ago we have created the componentized version of the WMEcoder.
If you are interested, contact BSquare for more details.

I dont think this to be free .. isnt it?

It is not. As you can imagine it is not my property but the compoany's

--
Regards,
KM, BSquare Corp.

Prakash437,

Something is not working with your access to the NG. You missed the reply,

although it is perfectly seen from here.

Anyway, here was my reply below.... (basically I asked you to provide your System Hive for review)

-------------------------


Nope, did not see you reply here.
Sometimes public newsgroup servers behave weird :-(


I just saw your component. The phase are indeed the ones you set.
does.)

Seems that your component's FBA generic command(s) phases get reset to 4500.
My very rough guess would be that this may happen because you have the

"Windows Installer Service" specified in the dependency list.

The "Windows Installer Service" installs the msiexec service at the 4500

FBA system phase (that is the FBA command just before your

own FBA command you saw in the log file).

Why your phases are getting reset - I don't have a clue.

I can't build your component here as I don't have your repository.

Would you mind send us (through the website) the "system" hive of the

built (pre-FBA) image? I want to take a look at the FBA

commands set up there.

--

KM,
BSquare Corp.

PS. A while ago we have created the componentized version of the WMEcoder.

If you are interested, contact BSquare for more details.

KM wrote:
Prakash437,

Are you sure you set FBA phases to something > 9000?

From your FBA log it seems that the phases were set somewhere between
2100 and 4500:


******************** 2100 phase *****************************
16:51:57 PM - [CallEntryPointThread]
C:\WINDOWS\system32\odbcconf.dll, DllRegisterServer


******************** Your FBA commands *****************************
16:52:03 PM - [FBALaunch] C:\WINDOWS\system32\msiexec.exe /regserver
(ExitCode: 0x0)
16:52:34 PM - [FBALaunch] C:\WINDOWS\system32\msiexec.exe /i
"C:\WINDOWS\system32\WMEncoder.msi" /qn (ExitCode: 0x641)

******************** 4500 phase *****************************
16:52:41 PM - [FBALaunch] C:\WINDOWS\system32\lodctr.exe
/c:C:\WINDOWS\system32\perfd009.dat /h:C:\WINDOWS\system32\perfi009.dat
/l:009 (ExitCode: 0x0)



If acceptable, you may want to attach your SLD here so that we could
take a look at it.

--
Regards,
KM, BSquare Corp.


Hello everyone,
I have 2 FBA generic commands, one executing an application
installer, and
the later deleting the installer file. Their phases are 9000 and
9100
respectively.

Ofcourse, these commands are executed and i get the desired
result. And out of curiosity when i checked the FBA log i find that
one of
the Generic command is executed, way too early (infact a few
minutes into
the FBA) and exits with an exit code:0x641. The installer actually
uses the
services of msiexec.exe. Here i provide that little part of FBA
log, which i
feel is fishy??

FYI, the same command is again executed finally successfully and
exits with
the code: 0x00.

Any ideas if there is anything wrong in it ?? Or is it some sort of
initializing ?? if yes why only this generic command, when i have
other
commands aswell.

Monday, January 31, 2005

16:49:08 PM - [FBASetProgressText] Setting PNP Flag...
16:49:55 PM - [FBAApplySecurityStringToRegKey] RegSetKeySecurity
Failed!
Error: 0x6
16:49:56 PM - [FBAReplaceSecurityInRegistry]
FBAApplySecurityStringToRegKey(009) #1 Failed!
16:50:07 PM - [FBASetProgressText] Initializing...
16:50:08 PM - [CallEntryPointThread] C:\WINDOWS\FBA\FBALIB.DLL,
FBAInitialize
16:50:08 PM - [FBASetProgressText] Setting SystemPrefix...
16:50:09 PM - [FBASetProductKey] Evaluation product key
16:50:10 PM - [FBASetProgressText] Initializing User Profiles...
16:50:22 PM - [CallEntryPointThread] C:\WINDOWS\FBA\FBALIB.DLL,
FBAStep1
16:50:23 PM - [CallEntryPointThread] C:\WINDOWS\FBA\FBALIB.DLL,
FBASetSetupInfo
16:50:24 PM - [FBASetProgressText] Installing System Security...
16:51:43 PM - [FBAInstallSecurity] Successfully set security!
16:51:45 PM - [CallEntryPointThread] C:\WINDOWS\FBA\FBASEC.DLL,
FBAInstallSecurityPhase1
16:51:45 PM - [FBASetProgressText] Registering Components...
16:51:46 PM - [CallEntryPointThread] C:\WINDOWS\system32\atl.dll,
DllRegisterServer
16:51:48 PM - [CallEntryPointThread]
C:\WINDOWS\system32\txflog.dll,
DllRegisterServer
16:51:49 PM - [CallEntryPointThread]
C:\WINDOWS\system32\netcfgx.dll,
DllRegisterServer
16:51:51 PM - [CallEntryPointThread]
C:\WINDOWS\system32\netman.dll,
DllRegisterServer
16:51:53 PM - [CallEntryPointThread]
C:\WINDOWS\system32\netshell.dll,
DllRegisterServer
16:51:57 PM - [CallEntryPointThread]
C:\WINDOWS\system32\odbcconf.dll,
DllRegisterServer

************************************** Note these lines
***********************************************************
16:52:03 PM - [FBALaunch] C:\WINDOWS\system32\msiexec.exe
/regserver
(ExitCode: 0x0)
16:52:34 PM - [FBALaunch] C:\WINDOWS\system32\msiexec.exe /i
"C:\WINDOWS\system32\WMEncoder.msi" /qn (ExitCode: 0x641)
************************************** Note these lines
***********************************************************

16:52:41 PM - [FBALaunch] C:\WINDOWS\system32\lodctr.exe
/c:C:\WINDOWS\system32\perfd009.dat
/h:C:\WINDOWS\system32\perfi009.dat
/l:009 (ExitCode: 0x0)
16:52:42 PM - [CallEntryPointThread]
C:\WINDOWS\system32\MSCTF.dll,
DllRegisterServer
16:52:44 PM - [CallEntryPointThread]
C:\WINDOWS\system32\rsaenh.dll,
DllRegisterServer
16:52:46 PM - [CallEntryPointThread]
C:\WINDOWS\system32\dssenh.dll,
DllRegisterServer

Thanks,
prakash

 

[Prakash437]

Hi ..
Thank you both ..

Sorry, i was away from my desk during the weekend ..

Anyway, look at the first few lines of the FBALog. You will notice:
17:36:30 PM - [FBASetProgressText] Setting PNP Flag...
17:37:19 PM - [FBAApplySecurityStringToRegKey] RegSetKeySecurity Failed! Error: 0x6
17:37:19 PM - [FBAReplaceSecurityInRegistry]

FBAApplySecurityStringToRegKey(009) #1 Failed!

I would like to refer you to the SP-2 release notes which says, this is a
harmless message and can be safely disregarded ..
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnxpesp2/ht
ml/XPESP2RNReleaseNotesForMicrosoftWindowsXPEmbeddedWithServicePack2.asp

I still believe something is wrong with your build. Particulary, could you

check NTFS Security permission set on the build directory

for this image?

The development system has only one user (Administrator). And i am set to
have all access rights. And can you explain how can this effect the
behaviour of FBA, of a CF drive, which is run under the target hardware ??

Regards,
Prakash.

 

[Prakash437]

PS. A while ago we have created the componentized version of the
WMEcoder.

It is not. As you can imagine it is not my property but the compoany's

ya .. I can understand .. the present component is working quite fine .. i
hope it should be enough ..

Anyway, thanks for the advice ..

Prakash

 

[KM]

Prakash,

Thank you both ..

Sorry, i was away from my desk during the weekend ..

Anyway, look at the first few lines of the FBALog. You will notice:
17:36:30 PM - [FBASetProgressText] Setting PNP Flag...
17:37:19 PM - [FBAApplySecurityStringToRegKey] RegSetKeySecurity Failed! Error: 0x6
17:37:19 PM - [FBAReplaceSecurityInRegistry]

FBAApplySecurityStringToRegKey(009) #1 Failed!

I would like to refer you to the SP-2 release notes which says, this is a
harmless message and can be safely disregarded ..
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnxpesp2/ht
ml/XPESP2RNReleaseNotesForMicrosoftWindowsXPEmbeddedWithServicePack2.asp

Oh, you are absolutely right. I guess the "Performance Counter Configuration" component is in your image.
Thanks for pointing that out. I missed that line in SP2 Rel.Notes

check NTFS Security permission set on the build directory
The development system has only one user (Administrator). And i am set to
have all access rights. And can you explain how can this effect the
behaviour of FBA, of a CF drive, which is run under the target hardware ??

I cannot explain that. I was just thinking loud that I never had the permission problems with the system hive from my builds (from
different machine!) but I did have such with your system hive which suprised me and I thought something might be wrong with your
build.

Your current issue with duplicated launch of an FBA command seems to be really wierd and any (even strange) hypothesis may be
helpful.

The real problem is that we do not have any good way to debug anything during FBA. Only some indirect trying.
I'd suggest you to try:
- Change FBA phase for the command to see if it has any affect when you set it to "system numbers" (< 8500).
- Change the commnad to launch CMD for debug purposes instead of .msi.
- Create a very simple (better minlogon/cmd based) image from scratch. Do not include anything you don't need in this debug
image. Even network stack may not be required. Add your FBA generic commands there and see if they are launched twice.

Sorry, don't have a solution for you.

 

[Slobodan Brcin \(eMVP\)]

I still believe something is wrong with your build. Particulary, could you

I cannot explain that. I was just thinking loud that I never had the permission problems with the system hive from my builds (from
different machine!) but I did have such with your system hive which suprised me and I thought something might be wrong with your
build.

I have them all the time but only with minlogon based pre FBA images. This is why I use regedit with system credentials. It apear
that system account has access to all registry entries in all cases which is not true for administrator.

Sorry, don't have a solution for you.

Neither do I :-(

If you want to play around with this problem let us know we can guide you with some sugestions based on feedback that you give us.

But if you want to speed process up and not to wait for FBA to complete each time I suggest you to connect remotely to this computer
trough windbg so you can see fba.log in real time on development computer.

Also like Konstanin said you can play with phase numbers, also you can set in offline registry that FBA already visited your command
and then you can observe behaviour during the FBA.
It might be important what will be reported and whether you will see 0, 1 or 2 entries regarding your command.

Regards,
Slobodan