Xythos xLinks Not Compatible

Written by backpacker on August 18, 2009 – 3:48 pm -

There is a way to link content to the Blackboard server that causes the download from Blackboard to Backpack to fail. This method is called Xythos, which uses link ids called xlinks. This method probably allows the content to be linked and utilized in a more efficient manner by the server, overall. However, this new method does not work with Backpack, so if the school changes to this linking method then instead of seeing the content in Backpack you will see errors like this:

………………………………………………………………………………..

Document Not Downloaded (Error)

Start (59.4 KB) was not downloaded because of the following server error: Moved Temporarily (Found)

To try to download it again now, click the “Download Now” button below.

………………………………………………………………………………..

Unfortunately, when you click the Download Now button you simply end up in a cycle. The content never shows up.

You can tell if your school is using Xythos by looking at the links to content. If they use Xythos the links will and in xlink ids (something like “xlink_id=XXXX”).

The only solution to this problem at the moment is for the school not to use the new linking method.


Posted in Compatibility, Download Errors, Errors | Comments Off

“Read” Status in Discussion Boards

Written by backpacker on July 14, 2009 – 12:39 pm -

Some of you may find when working in discussion boards that Backpack appears to lose the “read” status for previously read discussion board posts. Unfortunately, this is caused by a bug on some Blackboard servers. Some versions of Blackboard server ignore the read/unread status sent by Backpack.

I’m afraid there is not much you can do about this. Agilix has reported the problem to Blackboard, Inc., but it has not yet been resolved.

This is what happens (this all happens within 1-2 seconds):

  1. You read a post in Backpack; Backpack marks it as “read”
  2. When you sync with your Blackboard account, Backpack sends the “read” status to the server
  3. The server accepts the status without returning an error to Backpack
  4. The server then drops the status for some unknown reason (so it retains its “unread” status for the post)
  5. Backpack immediately attempts to re-sync with the server, requesting updates for all statuses
  6. The server sends the “unread” status back to Backpack (because it ignored the “read” status)
  7. Backpack changes its “read” status back to “unread” because that is what the server told it to do

There is no fix and no work around for this bug. Backpack will always sync to match what the server shows. So, for instance, if you were to go online to read the posts, they would change to “read” online. Then, when you sync Backpack with the server again, the status will change from “unread” to “read” in Backpack to match the server.

Trust me – Agilix knows how frustrating this bug is. It is frustrating to them, too! Unfortunately, the fix must be made on the server side by Blackboard, Inc.


Posted in Download Errors, Errors | Comments Off

Maximum Number of Activations

Written by backpacker on July 13, 2009 – 3:56 pm -

If you receive an error that says your key has been used the maximum number of times (below), don’t panic!

activation-maximum

This does not happen often, but when it does it usually indicates that (1) there is a firewall blocking Backack’s ability to validate its license, or (2) there is confusion about how the key works.

Firewall. Make sure you add Agilix Backpack as an exception to your firewall software. Also, if you run your computer on a corporate network you may want to ask your IT group to permit Backpack’s attempt to reach the license server. The URL is: http://license.agilix.com/backpack/backpacklicense.asmx

How the key works. The license key can only be used to activate two storage locations.

This means that you can either activate on the hard drive of two machines, or on the hard drive of one machine and a USB drive, or on a network drive and a USB drive, or on two separate directories of the same hard drive, etc. Reformatting a computer will also cause the system to think it’s a new location. The total storage locations for the key can only be two.

WHAT TO DO NOW: Contact Agilix Support and ask them to reset your key. But remember to correct the underlying firewall issue first, or it will just happen again.

If you have the need to regularly use the software on different machines then you might try using the software with a USB flash drive for storage. In that case you would never activate the software on the hard drive of the machine(s) you are using – only activate on the USB. You can find more information about that option in the tutorials at the official Backpack site:

http://backpack.agilix.com/3.0Tutorials_USB.aspx


Posted in Activation Key Errors, Errors | Comments Off

Invalid Key

Written by backpacker on July 13, 2009 – 3:47 pm -

If you receive the invalid key error below when trying to activate the software, double check your key. Note that the Agilix Backpack key will not include any letter O’s (only number zero). Note that some letters and numbers may be difficult to distinguish, such as B/8, S/5, and G/6, so double check and try again.

 activation-invalid-key

This error will only appear if (1) you enter your key incorrectly, (2) your key was once valid, but has since been rendered invalid (if you received a refund, for example), or (3) you received a key from Handango, but it was not fully processed and enabled by Agilix (this is rare, but has happened).

If you double check your key, but still cannot get it to activate, contact Agilix for further assistance.


Posted in Activation Key Errors, Errors | Comments Off

Setup Initialization Error

Written by backpacker on July 10, 2009 – 6:47 pm -

Sometimes during installation you might see a “setup initialization error.” This can be caused be a couple of different things: (1) the Backpack installation file is corrupted or was not completely downloaded before you tried installing it, or (2) you are missing Microsoft .NET 2.0.

Installation file. You may want to delete the Backpack “setup.exe” file you were using and download it again from the Agilix website here. Once you have redownloaded the file, try installing it.

Missing .NET 2.0. Microsoft .NET 2.0 (dotnetfx.exe) may be missing from your computer. This component from Microsoft is a prerequisite for running Backpack. If Backpack can’t find this on your machine before it installs it will try to send you out to get it from the Microsoft web site. Sometimes when you try to get this file, it results in a “Setup initialization error” or similar message. Most computers have this component already, so it’s usually not a problem. You can get it here if needed:

http://www.microsoft.com/downloads/details.aspx?FamilyID=0856EACB-4362-4B0D-8EDD-AAB15C5E04F5&displaylang=en

Save the file to your desktop and then install it. Then install Backpack after that. Once you have the required .NET component installed, you should be able to install Backpack easily.


Posted in Errors, Installation Errors | Comments Off

Error 1607: InstallShield Scripting Runtime

Written by backpacker on July 10, 2009 – 5:43 pm -

This is a frustrating InstallShield error. The Agilix Backpack software is delivered with InstallShield during installation, so when InstallShield breaks down that can be a big problem for getting Backpack to install!

Fortunately, you may be able to resolve the issue by following the steps that InstallShield has provided for this problem at:

http://consumer.installshield.com/kb.asp?id=Q108340

Good luck!


Posted in Errors, Installation Errors | Comments Off

Error 1327: Invalid Drive

Written by backpacker on July 10, 2009 – 5:36 pm -

This is a frustrating error. There used to be information in the Installshield knowledge base about how to correct this problem, but the information no longer appears to be found at the link below.

http://consumer.installshield.com/kb.asp?id=q110636

You may need to go to the Acresso Support site and search for “error 1327.” Acresso supports the Installshield product: http://support.acresso.com/Default.aspx


Posted in Errors, Installation Errors | Comments Off

Blackboard 9

Written by backpacker on July 10, 2009 – 5:20 pm -

To students:

Sorry folks, there is no compatibility with Blackboard 9. Blackboard removed the server component that facilitates the connection, called Mobilizer, from that version of the server. It is unlikely that Agilix will be able to re-develop that component as a building block for the new version of the server.

If you are currently using Backpack with Blackboard 7.x or 8.x then be aware that when your school upgrades to version 9 you will no longer be able to connect with Backpack.

To educators:

Agilix does not support the server-side code (”Mobilizer”) that is required to permit the connection between Agilix Backpack and the Blackboard server. That code, managed by Blackboard, Inc., is currently built into Blackboard server versions 7 and 8. However, Blackboard has decided to drop the Mobilizer from version 9, so Backpack will not be able to connect to that version.

Agilix develops others solutions that provide similar functionality, but not on the Blackboard platform. If you would like to learn more you can find more information about the solutions here: http://www.agilix.com/products.html and http://www.brainhoney.com/

There is also an instructor testimonial on YouTube here (this is a high school implementation): http://www.youtube.com/watch?v=PSA3Ug2jXF4


Posted in Compatibility, Connection Errors, Errors | Comments Off

64-bit Systems

Written by backpacker on July 10, 2009 – 4:25 pm -

Sorry guys – Backpack does not officially work with 64-bit systems.

If you try to install Backpack on a 64-bit machine you might run into an error 0X800F0214 (or similar).

Unfortunately, there are no current plans for a new release that will install natively on 64-bit systems. However, you might be able to get it to work by setting the 32bit .NET 2.0 runtimes as default fallback. The following link may be helpful:

http://social.msdn.microsoft.com/forums/en-US/phoenix/thread/9a43e9a1-a744-4a1a-bb34-3604254c126b/

NOTE: The link above appears to show you how to set your system to use the 32-bit CLR for .NET; however, other sources that advise against doing that. You will need to do some research and make your own determination.

Officially, Backpack is not compatible with 64-bit systems.


Posted in Compatibility, Installation Errors | Comments Off