This is happening at a customer's site. We installed SQL
Anywhere 11 and configure a service to start up
automatically. My default install/configuration on the C:
drive works fine. Customer wants the database on his NAS
drive which is mapped to M. I open scjview, do properties of
the service, configuration tab and changed the path to the
DB in 'parameters to executable'. Then I try to restart the
service it tells me that the file does not exist and
displays the path. I tried remapping the drive to another
letter, I tried using UNC path, tried a different path on M
but I get the same error message. I can connect using
scjview and dbisql using the same mapped drive. This was
previously setup this way using SQL Anywhere 6.0.3 and we
just converted them. I have done this many times before and
never had a problem. I change the path back to the c: drive
and the service starts up fine. Any ideas?

Hi Lance,

I assume the SA11 database server service is started underneath the
"LOCAL SYSTEM" account? If so, this account generally does not have
access to network resources - particularly network resources that
require a user login (e.g. a share in the domain, NAS, etc.)

---

There are two general options to get around this behaviour:

1. Don't run the database as a service
2. Run the service underneath a domain account that has access to the
network resource (See: dbsvc -a:
http://dcx.sybase.com/index.php#1101...utilities.html
)

Also of note, you should ensure that the NAS conforms to these
requirements: http://www.sybase.com/detail?id=1034790

Cheers,

Lance Douglas wrote:
--
Jeff Albion, Sybase iAnywhere

iAnywhere Developer Community :
http://www.sybase.com/developer/libr...ere-techcorner
iAnywhere Documentation : http://www.ianywhere.com/developer/product_manuals
SQL Anywhere Patches and EBFs :
http://downloads.sybase.com/swd/summ...&timeframe =0
Report a Bug/Open a Case : http://case-express.sybase.com/cx/