Hi all,

I built an app with the "Platform target" of x86. Then I installed it as a
Windows Service. When it's running, I can see in the Task Manager that the
executable has "*32" following it, which I think means it's running in 32bit.
But after I changed the log on account of the service, the "*32" disappeared
and it's running in 64bit. Is there any way to fix this? I need to run it in
32bit.
Thanks.

--

Thanks.

Daniel

Hi Daniel,

Do you mean that if you changed the running account of the Windows Service,
the service will change from WOW64 into 64bit? Then, which account do you
change to?

Have you tried this on a simple new Windows Service project? If so, please
feel free to provide the detailed steps for reproducing, I will setup a
64bit OS machine to perform local reproduce for this problem. Thanks.

Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Hi Jeffrey,

I've changed to both an AD account and the Network Service account, both
will make the process running without the "*32" in the Task Manager. And my
proejct is simple. I'm confused by the "Target platform" selection, as I've
already selected x86, is this application still capable of running as a 64bit
app?
I didn't do anything special about the service, so reproducing it could be
simple.

--

Thanks.

Daniel


""Jeffrey Tan[MSFT]"" wrote:

> Hi Daniel,
>
> Do you mean that if you changed the running account of the Windows Service,
> the service will change from WOW64 into 64bit? Then, which account do you
> change to?
>
> Have you tried this on a simple new Windows Service project? If so, please
> feel free to provide the detailed steps for reproducing, I will setup a
> 64bit OS machine to perform local reproduce for this problem. Thanks.
>
> Best regards,
> Jeffrey Tan
> Microsoft Online Community Support
> ==================================================
> Get notification to my posts through email? Please refer to
> http://msdn.microsoft.com/subscripti...ult.aspx#notif
> ications.
>
> Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
> where an initial response from the community or a Microsoft Support
> Engineer within 1 business day is acceptable. Please note that each follow
> up response may take approximately 2 business days as the support
> professional working with you may need further investigation to reach the
> most efficient resolution. The offering is not appropriate for situations
> that require urgent, real-time or phone-based interactions or complex
> project analysis and dump analysis issues. Issues of this nature are best
> handled working with a dedicated Microsoft Support Engineer by contacting
> Microsoft Customer Support Services (CSS) at
> http://msdn.microsoft.com/subscripti...t/default.aspx.
> ==================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>

Hi Daniel,

Thank you for the feedback.

Yes, in a Win2003 64bit application, I can reproduce this problem. I will
spend some more time on it and get back to you ASAP. Thanks.

Additionally, what account do you use so that you can see "*32" in task
manager?

Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Hi Daniel,

Sorry for letting you wait, I am out of office yesterday.

I suspect this may be a problem of Task Manager because Process Explorer
will report different result as Task Manager. You may download Process
Explorer from the link below:
http://technet.microsoft.com/en-us/s.../bb896653.aspx

Using Process Explorer, if you add the "Image Type(64 vs 32bit)" column in
the process list, we will see that this .Net service process is identified
as 32bit instead of 64bit. Also, in the DLL panel of this Windows Service,
you can see the service Exe is also identified as 32bit image type(You
have to added ). Furthermore, you see WOW64.dll, WOW64cpu.dll and
WOW64Win.dll in the service process. So it should be a 32bit WOW64 process.

I assume this may be a problem of task manager. Thanks.

Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Thanks Jeffrey. The reason I need it to be 32bit is that I will use
ManagedDTS to execute a dtsx file which requires 32bit. The problem is, no
matter what's wrong with the task manager, the ManagedDTS recognizes the
process as a 64bit too(I guess, because it fails if I change the user account
to anything other than the default). Do you have any idea on what's going on
with the ManagedDTS? Or do I have any choice to force it execute a package in
32bit?

Hi daniel,

Sorry, I have no experience over ManagedDTS. You'd better post in
microsoft.public.sqlserver.programming newsgroup to get help. Thanks.

Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.