> $ ./tinyerp-server -d base_name --init=all I did exactly what you proposed. - I used dropuser and dropdb to clean up previous tinyerp user and database - I created the tinyerp system user and performed all other steps you outlined.
Result: - Message "INFO:init:could not connect to database 'b_host'!" NO LONGER APPEARS. Excellent. - "INFO:init:connecting to database" appears during tinyerp-server startup. Excellent. - No error appears while starting up the server. - Windows TinyERP client, File-Connect, the dialog shows message "Could not connect to server!" in the Database field. I captured the TCP communication between Linux server and Windows host. Here is the result: POST /xmlrpc/db HTTP/1.0 Host: 192.168.1.1:8069 User-Agent: xmlrpclib.py/1.0.1 (by www.pythonware.com) Content-Type: text/xml Content-Length: 98 <?xml version='1.0'?> <methodCall> <methodName>list</methodName> <params> </params> </methodCall> HTTP/1.0 404 Not Found Server: BaseHTTP/0.3 Python/2.5.1 Date: Tue, 16 Oct 2007 13:35:27 GMT Content-type: text/plain Content-length: 12 No such page All captured communication is over port 8069. Nothing but the above communication takes place before the Client reports "Could not connect to server!" Is this related to the fact that I use Python 2.5.1 ? Should I use a different, older version of xmlrpc library? -- Milos Prudek _______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman/listinfo/tinyerp-users
