Moving from evaluation version repository

[Graham Dunn]

When I first started with XPE studio, I had built a few components into
my repository that I wanted to keep, so when I moved to a licensed copy
of Embedded studio, I uninstalled the studio, but just upgraded the
repository, thinking I'd save myself some time.

However, it appears that was a mistake, as I still see "evaluation
version" on the splash screens, and have nowhere to enter in the runtime
license information for images under Settings.

Is there a better way to solve this problem than to delete everything
and reinstall? I'm running my repository on an external machine (the
original plan was to have several developers share a repository).

Thanks,
Graham

 

[Sean Liming \(MVP\)]

You need to wipe out the whole repository and database, and install the full
release version. Then just import your SLD files for your components.

--
Regards,

Sean Liming
www.sjjmicro.com / www.seanliming.com
Book Author - XP Embedded Advanced, XP Embedded Supplemental Toolkit

 

[Graham Dunn]

You need to wipe out the whole repository and database, and install the
full release version. Then just import your SLD files for your components.

OK, I've created a new database instance, using SQL Express, and can
connect to it locally, but can't login from a remote workstation.

I've created a user (DOMAIN\username) on the database config
(Security->Logins), and have assigned the WES_Importer role in the
MantisSQLDB database (MantisSQLDB->Security->Users).

Any advice?

 

[Graham Dunn]

OK, I've created a new database instance, using SQL Express, and can
connect to it locally, but can't login from a remote workstation.

I've created a user (DOMAIN\username) on the database config
(Security->Logins), and have assigned the WES_Importer role in the
MantisSQLDB database (MantisSQLDB->Security->Users).

Any advice?

Following up: I can connect to the database from ODBC, using windows
authentication, and see the database with all the tables just fine.

When I try to connect from Component Database Manager, I see this in the
SQL server logs:

2007-07-24 12:06:28.40 Logon Login succeeded for user
'HARRIS\gdunn01'. Connection: trusted. [CLIENT: xxx.xxx.xxx.xxx]
2007-07-24 12:06:28.56 Logon Login succeeded for user
'HARRIS\gdunn01'. Connection: trusted. [CLIENT: xxx.xxx.xxx.xxx]
2007-07-24 12:06:29.13 Logon Login succeeded for user
'HARRIS\gdunn01'. Connection: trusted. [CLIENT: xxx.xxx.xxx.xxx]
2007-07-24 12:08:47.87 Logon Login succeeded for user
'HARRIS\gdunn01'. Connection: trusted. [CLIENT: xxx.xxx.xxx.xxx]
2007-07-24 12:08:47.87 Logon Error: 18456, Severity: 14, State: 16.
2007-07-24 12:08:47.87 Logon Login failed for user
'HARRIS\gdunn01'. [CLIENT: xxx.xxx.xxx.xxx]

Is there any information on what Component Database Manager is trying to
do here?

Graham

 

[Graham Dunn]

OK, I've created a new database instance, using SQL Express, and can
connect to it locally, but can't login from a remote workstation.

I've created a user (DOMAIN\username) on the database config
(Security->Logins), and have assigned the WES_Importer role in the
MantisSQLDB database (MantisSQLDB->Security->Users).

Any advice?

Following up: I can connect to the database from ODBC, using windows
authentication, and see the database with all the tables just fine.

When I try to connect from Component Database Manager, I see this in the
SQL server logs:

2007-07-24 12:06:28.40 Logon Login succeeded for user
'HARRIS\gdunn01'. Connection: trusted. [CLIENT: xxx.xxx.xxx.xxx]
2007-07-24 12:06:28.56 Logon Login succeeded for user
'HARRIS\gdunn01'. Connection: trusted. [CLIENT: xxx.xxx.xxx.xxx]
2007-07-24 12:06:29.13 Logon Login succeeded for user
'HARRIS\gdunn01'. Connection: trusted. [CLIENT: xxx.xxx.xxx.xxx]
2007-07-24 12:08:47.87 Logon Login succeeded for user
'HARRIS\gdunn01'. Connection: trusted. [CLIENT: xxx.xxx.xxx.xxx]
2007-07-24 12:08:47.87 Logon Error: 18456, Severity: 14, State: 16.
2007-07-24 12:08:47.87 Logon Login failed for user
'HARRIS\gdunn01'. [CLIENT: xxx.xxx.xxx.xxx]

Is there any information on what Component Database Manager is trying to
do here?

Graham

The answer here was that I had only upgraded the eval version of the
tools, which try to connect to a database called "MantisSQLDBeval',
where as the full version connects to a database called 'MantisSQLDB'.
Database wasn't there, error message was less than helpful.

I deleted the installed eval->full upgraded tools, and installed from
the full CDs. Things work fine now.

Graham