topic Re: LocalServer.Initialize() throws error 267 -The directory name is invalid in ArcGIS Runtime SDK for WPF (Retired) Questions

LocalServer.Initialize() throws error 267 -The directory name is invalid

VincentDolan — Tue, 18 Sep 2012 20:19:50 GMT

When I call LocalServer.Initialize(), it throws: "The directory name is invalid" (error # 267)

I've used ProcessMonitor and see the last entry before the errror occurs is
Operation: CreateFile
Path: C:\longpathtomyproject\MyProject\bin\Debug\ArcGISRuntime1.0\LocalServer64\bin
Result: PATH NOT FOUND
Detail: Desired Access: Read Attributes, Disposition: Open, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a

My deploment folder has the expected structure:
ArcGISRuntime1.0

Client32

Client64

Resources

I've tried to manually create the LocalServer64\bin folder being complained about above, with no better results.

Any suggestions?
Thanks.

Re: LocalServer.Initialize() throws error 267 -The directory name is invalid

MichaelBranscomb — Wed, 19 Sep 2012 08:07:57 GMT

Hi,

What are you building your application as?

x86 => Will require Client32 and LocalServer32 directories within the ArcGISRuntime1.0 directory.

x64 => Will require Client64 and LocalServer64 directories within the ArcGISRuntime1.0 directory.

Any CPU => Will require Client32 & LocalServer32 OR Client64 & LocalServer64 directories within the ArcGISRuntime1.0 directory depending on the OS architecture of the machine.

But you should not be manually creating those directories - you use the Deployment Tool to build your runtime deployment with the appropriate components for your chosen architecture(s).

Cheers

Mike

Re: LocalServer.Initialize() throws error 267 -The directory name is invalid

VincentDolan — Wed, 19 Sep 2012 12:22:54 GMT

Mike, thanks for the response, you pointed me to the right place.

I had copied files from a deployment that had been built without ticking the "Local Server" checkbox. Calling LocalServer.Initialize() then threw the Error 267 "The directory name is invalid". Using a deployment built with that box checked, all is well.