Problem generating application using GUI Interface

, ,
1

When I am generating an application using the GUI generator, I am getting the following error.

Can anybody please help?

Thank you

Error reading schema from Tamino: query failed: xs:schema[xs:annotation/xs:appinfo/tsd:schemaInfo/tsd:doctype/@name=‘SECTOR-INFORMATION’][xs:annotation/xs:appinfo/tsd:schemaInfo/tsd:collection/@name=‘sectorlatest23’]: com.softwareag.tamino.db.API.accessor.TQueryException
Response could not be built
NestedException:NestedException:Exception during updating transaction mode!
NestedException:Transaction mode cannot be updated. No appropiate transaction state obtained from Tamino!Local Transaction Mode.
Session State sessionId= 11 sessionKey=13444
NestedException: Response could not be built
NestedException:NestedException:Exception during updating transaction mode!
NestedException:Transaction mode cannot be updated. No appropiate transaction state obtained from Tamino!Local Transaction Mode.
Session State sessionId= 11 sessionKey=13444…aborted

2

Which version of X-Application and Tamino do you use? X-Application 3.1.2 does not support Tamino 2 schemas …

Michael

Software AG Germany, Darmstadt

3

I am using Tamino 3.1.1.1
Xapplication 3.1.1

The interesting thing is that I have just installed Tamino onto a new server and have created databases underneath them. If I try and generate applications on this server, it does not work, if i create an application on the old server it works fine.

is there a problem if tht database server has the URL http://localhost:8060/tamino/mydb

Thanks

4

The URL with :8060 should be ok.

Could you please adjust your env.cmd (i.e. set TAMINO_URL for the new Tamino) and run X-Application’s setup again. Maybe this solves your problem …

Michael

Software AG Germany, Darmstadt

5

Did that. still not working.

6

Hi there.

I have a couple of questions…

You mentioned installing Tamino on a new server. Which version of Tamino was installed on the old server - also 3.1.1.1?

Which webserver is configured for Tamino on the new server?

How did you create your schema(s) in the new Tamino database?

What does the query return if you execute it directly in a Browser?
http://localhost:8060/tamino/mydb/ino:collection?_xql=/xs:schema[xs:annotation/xs:appinfo/tsd:schemaInfo/tsd:doctype/@name=‘SECTOR-INFORMATION’][xs:annotation/xs:appinfo/tsd:schemaInfo/tsd:collection/@name=‘sectorlatest23’]

Thanks,
Trevor.

7

I am using Tamino 3.1.1.1 on the old and the new machine. Both are configured to work with IIS. IIS runs on port 8060 on the new server whereas it runs on port 80 on the old machine. I created the database on the new server from a backup from the old machine database.

I just noticed one thing. Even though I can see all the schemas I defined throught the browser, I cannot see the contents of ino:collection if I type
http://localhost:8060/tamino/mydb/ino:collection?_xql=/

it comes up with page cannot be displayed. where this works fine on the old server. Have I missed something in the configuration?

Any help would be much appreciated.

Thank you

8

hi,

are you even getting anything from that new database?
that is: if you create a new database from scratch, is it accessible? can you insert/retrieve data from it?
does the database in question at least react to the following query:
http://localhost:8060/tamino/mydb?_diagnose=ping

regards,
andreas f.

9

Hey there,

I think that Andreas is on the right track - check that the database can be contacted using the diagnose=ping command.
(Perhaps you might also try the query “/*”, as I’m not exactly sure what “/” should return…)

Assuming the database can be contacted, you could next take the Schema Editor and double check that the “SECTOR-INFORMATION” doctype is defined in a Collection called “sectorlatest23”.

Cheers,
Trevor.

10

Everything else is working except when requesting for ino:collection.

http://localhost:8060/tamino/mydb/ino:collection?_xql=/

It comes up with page cannot be found

I think it is more of an IIS issue since in the logs for my request, I am getting . UrlScan had been installed on the machine unlike the old machine.

I will be changing the IIS settings tomorrow and will try it again.

Thank you

11

Yes the reason why XApplication was not working was because of UrlScan Installed on the new server. Changed it’s configuration and everything is working fine now.

Thank you very much for all your help.

12

Hello,

this topic will be moved to the Assistance Forum in the next days.
The assistance forum is intended to be used for technical questions and answers.

Thank you for your understanding.

Regards,
Christian.