One reason for this could be that your account does not have access rights to the MS SQL server. Even if this is your administrator account, this does not automatically mean that this account has access rights to the MS SQL server. Another possible reason could be that the MS SQL server was not configured to allow remote access or allow access via Windows authentication. Both can be configured in your SQL Management Studio.
Open the "Microsoft SQL Server Management Studio" and create a new login at "Security > Logins" (right click > "New Login"). You can now decide to choose "SQL Server Authentication" (recommended) or "Windows Authentication" on the page "General" of the shown dialog:
1. "SQL Server Authentication": Enter a new "Login name" and a secure "Password" for the new account. Also deactivate the option "Enforce password expiration".
2. "Windows Authentication": Enter an existing user account from your "Active Directory" as "Login name". You can use the button "Search" beside the edit field.
In both cases: Choose your SpaceObServer Database as "Default database". On the page "User Mapping": Check-mark the SpaceObServer database and add the database role "db_owner".
Note: To allow the access via "SQL Server Authentication" you need to choose "SQL Server and Windows Authentication mode" as "Server authentication" on the "Security" page of your SQL Server properties (right click on the SQL server > "Properties").
Unfortunately,the Netware Client for Windows provides no information about compression rateor file ownership to the regular Windows API. So developers for Netware have toadd a special support functionality. We will provide this functionality in alater version of SpaceObServer. All the other functions are availableon Netware drives, too.