Robot Upgrade from 2001A to 2002.05.00 and from MS Access to SQSLAnywhere
User (Russell_Lewis@insession.com.nospam) posted:
Has anybody had this experience and might be able to troubleshoot for me
here please? My software and projects are on on the same NT4 (SP6) server
(had to manually move the projects from another server first).
I have had a number of issues come up here, and have managed to work
through most of them including:
1. Creating an SQL server - I kept getting the message "Error 1812 -
Specified image file did not contain a resource section" and the service
wouldn't start. I got around this by configuring the service to start
manually instead of automatically. I think there is also a problem if you
try to use a server name longer than 8 characters.
2. After (finally) successfully copying the project from another server,
editing all the necessary project.dat, datastore.dat and other
yadayada.rtxml files, upgrading the MS Access datastores from 2001A to 2002
and then converting from Access to SQLAnywhere, I tried to logon to the
shiny new project using my shiny new 2002 Robot client machine to get
"Unable to connect to project". So going into Rational Adminstrator on the
client machine, sure enough, I can connect to project there, but the when I
click on Users folder I receive the error "Connection to test user group
server could not be established".
This is the latest point at which I am stuck. Rational support in Sydney
have no ideas for me - we have been checking the server configuration,
tried creating new projects etc to no avail.
I note that John at GDI Infotech wrote about a very similar (same?) problem
on 21 Dec 2001, but I have not been able to find any reply he might have
Thanks for your help.
Insession Labs Pty Ltd
Re: Robot Upgrade from 2001A to 2002.05.00 and from MS Access to SQSLAnywhere
User (firstname.lastname@example.org) posted:
Have you tried creating a new "datastore" (test repository)? If you can
do this AND connect/open it, I'd say something went awry with the
migration. If the migration went sour, you might try to copy your test
assets into the new repository a chunk at a time.
If this also fails, you might try creating an Access-based datastore to
verify that you are doing everything correctly.
I've avoided migration/upgrade issues by not using the built-in VP's.
This way, all I have to do is copy library and script files (manually),
then register them in the new repository database.