Rob,
Yup. That is WinLogon. And that is a good sign as you will definitely be able to fix the problem then.
I've tried the net use command without any difference.
I think I'm getting closer to my problem. I noticed that the "Named
Service Provider" field is empty under the "Client for MS Networks"
entry in the netwrok configuration properties dialog box. I found an
entry on MSDN that imples the image was built with out the RPC named
service component present
http://support.microsoft.com/default.aspx?scid=kb;en-us;883104
When I change the entry to "Windows Locator" I have to reboot and upon
rebooting the selection is blank again.
Great finding and interesting article. I don't want to speculate on it until you give it a try but I am thinking the Locator is not
the cause for the issue.
But who knows for sure untill it's tested
Before you reboot (btw, make sure you are not running enabled EWF!) make sure the [HKLM\SOFTWARE\Microsoft\Rpc\NameService] exists
and "Endpoint" value there set to "\pipe\locator".
I'm working with Advantech to fix this but is there a way that you know
In case it is getting to long to get this fixed through manufacturer, you can always build your own image and replace the current
image on the device.
At least you can do that for testing purposes.
All you need to do is:
- Get XPE ToolKit (Eval would work)
- Run TAP on the device under current image and import and process PMQ
- Create a Winlogon image based on the platform macro component you get on the previous step
- Include whatever components you would like to add (RPC Name Service, etc.)
- Change the Windows directory in the Configuration Trget Device Setting to something like \Windows2, also change all other
directories there to something unique (e.g., Document annd Setting2, etc.)
- Build the image
- Copy the image (everything except files under root) over network (for example) to the device storage media (I am assuming
you've got there enough space to fit both images)
- Change boot.ini to switch to boot from \Windows2 ARC path
- Reboot and watch the FBA process. Test, analyze and debug the image as you'd want to
Since you know that XPe runs on the device already, it may take just a couple of hours for you to build a new image.
of that I can check to see if the RPC service is present. In the FBAlog
file there is an entry that shows rpcrt4.dll is registered.
For the RPC just check the registry under [HKLM\Software\Microsoft\Rpc] to see what's registred.
And certainly check if the RPC services are started.
The rpcrt4.dll belongs to "RPC Local Support" which is likely is in your image.