Hello All!

I am hoping that someone might give a hand with this problem I am
having. I have installed the EBF 10.0.1.3831 to my Mobilink server
and everything went well. Now wish to apply the same EBF to my remove
dbs which are currently on 10.0.1.3619 but I get an error message that
I am hoping you can help me with. The error message is:

---------------------------
Feature transfer error
---------------------------
Feature: Network database client
Component: 64-Client
File: <PLATFORM_DIR_SA>\
Error: The filename, directory name, or volume label syntax is
incorrect.


---------------------------
OK
---------------------------

Does anyone have any idea on what this trying to tell me. Please keep
in mind that I am relatively new to Sybase as guy who used to deal
with all of this stuff is no longer with the company and I trying to
quickly get up to speed with all this.

Thanks,
Jen

Jen,

jenniferdewolfe (AT) gmail (DOT) com wrote:
Okay, so there's a bit of explanation that will need to go into this...

The issue is that you will not be able to directly apply the EBF to your
deployed database installs. The reason this is the case is because the
installer that was used to build those deployed copies was our
"Deployment Wizard" utility. (See:
http://www.ianywhere.com/developer/p...s-4228164.html
)

What the utility does is it takes a full SQL Anywhere install (at
whatever build it's currently at) and bundles the relevant files into an
MSI. We do not consider this install to be a "full install" of our
product and we do not allow these deployments to be patched with our EBF
patch utility.

What you'll need to do instead is to take a *full* SQL Anywhere
deployment, patch it (I assume your MobiLink server is this kind of
install since it was patched successfully!), then use the Deployment
Wizard AGAIN to generate new MSIs to be sent out to your clients. These
MSIs will have the updated build files inside of them, and they can be
installed over the old deployed copies.

Hope this helps!

Regards,

--
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

On Feb 26, 9:22*am, "Jeff Albion [Sybase iAnywhere]"
<firstname.lastn... (AT) ianywhere (DOT) com> wrote:
Hi!

Building the MSI file works great but I do have more quick question.
I have several environments set up each with their own set of Remote
DBs and Mobilink Server (Development, Testing, Staging, and
Production). Do I have to create MSI files for each envirnoment of
their respective Servers or am I able to create the MSI off one server
and apply it every where, assuming of course that all the Mobilink
servers have the Applied EBF upgrade.

Thanks
Jen

Jen,

jenniferdewolfe (AT) gmail (DOT) com wrote:
The MSI is just the SQL Anywhere program files, and these should be "the
same" across all of your installations. The only "gotcha" that I'd watch
out for is if the deployments are licensed differently and require
different license files. (i.e. run "dblic" on the license file on the
remote before deploying to make sure they're all the same. See:
http://dcx.sybase.com/html/dbdaen10/...utilities.html

)

Regards,

--
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

On Mar 3, 10:52*am, "Jeff Albion [Sybase iAnywhere]"
<firstname.lastn... (AT) ianywhere (DOT) com> wrote:
Hi Jeff
Does the License Number, UserName, and Company have to be the same or
can they be different so long as the Key is the same?
Thanks,
Jen

Jen,

This is really subject to your deployment license and your sales
agreement with Sybase iAnywhere. (i.e. You shouldn't authorize more
"seats" than you have paid for).

The User Name / Company is less important information - these are for
your own branding purposes.

The license that's being deployed should be the license that your sales
rep has said is okay for deployment (i.e. not a "developer copy").

jenniferdewolfe (AT) gmail (DOT) com wrote:
If you're still unsure, you should contact your sales rep for clarification.

Regards,

--
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