It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×1,192

question asked: Jan 31 '11, 6:09 a.m.
question was seen: 9,560 times
last updated: Jan 31 '11, 6:09 a.m.

Related questions

BF 7.1.2.1 command cause Error 193: 0xc1 ?!?!?!

0
Antonio Bonanni (111●17●17) | asked Jan 31 '11, 6:09 a.m.
Hi all,

i'm experiencing this strange behaviour after installation: i installed BF 7.1.2.1 in Windows Server 2003 R2 ( all is ok, no errors during installation ) and the agent on the same machine. I test the BF->Agent connectivity and no issue or strange behaviour: i run a project and the agent show on the cmd console failed to spawn bfagent ( the agent was launched with the bfdispatch -d option ). After this error i close the agent and restart the BF Management Console and the error 193: 0xc1 ( Windows Error during service startup ) was shown. The only workaround is to reinstall the agent and the management console in another system path using the existing BF database ( i tried to restore / reinstall BF on the same path but the error 193 was shown again ). This is the only workaround i founded.
Anyone has the same strange behaviour ?

Thanks

4 answers

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Robert haig (1.0k●1●6) | answered Jan 31 '11, 11:09 a.m.
FORUM MODERATOR / JAZZ DEVELOPER
Hi all,

i'm experiencing this strange behaviour after installation: i installed BF 7.1.2.1 in Windows Server 2003 R2 ( all is ok, no errors during installation ) and the agent on the same machine. I test the BF->Agent connectivity and no issue or strange behaviour: i run a project and the agent show on the cmd console failed to spawn bfagent ( the agent was launched with the bfdispatch -d option ). After this error i close the agent and restart the BF Management Console and the error 193: 0xc1 ( Windows Error during service startup ) was shown. The only workaround is to reinstall the agent and the management console in another system path using the existing BF database ( i tried to restore / reinstall BF on the same path but the error 193 was shown again ). This is the only workaround i founded.
Anyone has the same strange behaviour ?

Thanks


You should open a PMR on this. support will want to collect some system specifics and path specifics to see if they can reproduce in house. You may have uncovered a defect in the code that creates the windows service entry. If you have, we will want to create test cases around this for future releases.
0
permanent link
Antonio Bonanni (111●17●17) | answered Feb 01 '11, 5:03 a.m.
Hi rhaig,

thank you for your reply. I solved the issue making a new fresh install: i've also used the command line tools ( bfexport and bfimport ) to restore the projects and the environments but not all the configuration was restored. I think the problem was caused by a database corruption: when i reinstalled and launched the same project ( that make the problem ) no issue was generated. Now we have to reconfigure some Environments and Servers.
0
permanent link
Robert haig (1.0k●1●6) | answered Feb 01 '11, 10:24 a.m.
FORUM MODERATOR / JAZZ DEVELOPER
Hi rhaig,

thank you for your reply. I solved the issue making a new fresh install: i've also used the command line tools ( bfexport and bfimport ) to restore the projects and the environments but not all the configuration was restored. I think the problem was caused by a database corruption: when i reinstalled and launched the same project ( that make the problem ) no issue was generated. Now we have to reconfigure some Environments and Servers.


you can get environments and servers on export also. they're not added by default, but you can specify the -s flag to get servers, and on import also -s. environments are exported attached to projects being exported, but you need to specity -e on bfimport. 






$ ./bfexport -h

Usage: bfexport -l

or:

bfexport [-c comment] [-f filename] [-g] [-s] [-L] [-n] <Project> <Version>

Options :

-l : Lists all projects in the system and their project UUID.

-c : Add a comment to the output XML.

-f : File to write the output to.

-g : Include group users (requires -s).

-s : Include all servers.

-C : Include servers collectors (requires -s).

-L : Include LDAP configuration.

-n : Include template notifications.

Project must be a valid project name or project UUID.





$ ./bfimport -h

Usage: bfimport [opts] [file]

[opts] are:

-L    list xml file contents

or:

-p    import projects

-I    include chained projects

-S    import selectors

-s    import servers

-e    import environments

-c    import classes

-C    import collectors

-u    import users

-T    import notification templates

-f    import filters

-d    import ldap domain settings

-r    replace rather than rename imported items
0
permanent link
Jaegon Yoo (96●1●13●14) | answered Nov 09 '11, 8:43 p.m.
I faced same problem.

When agent starts, it says 'Error 193: 0xc1'.

I tried to find the reason but failed.

So I tried to reinstall in same folder which was useless but when I installed in different folder, it worked.

Very strange. But I don't know why.

If anyone face same problem, try a workaround.

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.