Newbies musicofnote Posted January 2, 2005 Newbies Posted January 2, 2005 Hello! This is silly - probably pilot error. Could not get FMPro 7 Server installation to work - first because Firewall was turned on. Now it's off and I can access databases from other computers. Great. next step is/was to get Web Access going. Installed WebPublishing, and the config web site can communicate with the Server. Or so it says. Problem is, in the FMP 7 Server Admin Program / Clients / Filemaker WebPublishing engines, when I add the same identifyer and Passcode as for the WebConfig, I get no IP for the Web Admin Console. Consequently, when I try to actually access the DBs via Safari, they are listed for access, but when I try to open them, I get a "Javascript unkown error 802" I have the feeling I'm 1-2 mouse clicks from getting this horror going. And the only reason why I'm doing this is to document the bloody thing. I had to give up at work adn call a consultant to get the same set-up going there, but he went too fast for my note-taking :-(( Thanks in advance for any H E L P anyone can offer.
PoweredbyFm7 Posted January 2, 2005 Posted January 2, 2005 Your problem is my problem. Sometimes i have been configured Filemaker Server Advanced. But mostly, i have not succeded. Filemaker Inc. can solve this problem, i hope. If you have a solution for this problem, please help me.
Newbies georgemayne Posted January 11, 2005 Newbies Posted January 11, 2005 also have this problem no fix yet....
armeen Posted January 25, 2005 Posted January 25, 2005 try the identifier and passcode both in lower case.
armeen Posted February 8, 2005 Posted February 8, 2005 i just came across this problem on a client machine (os x) that the ip address would not show in front of the identifer and passcode. here are my troubleshooting steps to fix the problem: 1. remove the old identifer and passcode entirely. 2. create a new idnetifer and passcode. (at his point you still don't see the ip address) 3. uninstall the web publishing engine via fm server advance cd. (critical step) 4. restart your machine. 5. reinstell the web publishing engine via fm server advance cd. 6. restart your machine. 7. go back to the fm server admin utility where the identifier and passcode are listed. now the ip address of your server should be listed there. (similar to this: http://xxx.xxx.xxx.xx:80/fmi/config please post back to see if that worked for you or not.
infiniteg Posted February 11, 2005 Posted February 11, 2005 I'm having the same problem. Here's what I did: 1) Installed & tested FM Server 7 on computer running W2K Server 2) Installed WPE & Admin Console on same computer as Server 7 3) Rebooted machine 3) Opened http://localhost/fmi/config in IE web browser 4) Set username/password for the admin console 5) Set username/password for WPE <--------problem starts here---------> The next page that loaded read ... "The Publishing Engine is not responding. If the Publishing Engine has not yet been configured, _click_here_ to continue." So I clicked the _click_here_ link and was taken to a page that asked me to set the web publishing engine address. I entered localhost and clicked the continue button. The next page prompted me for a username and password. I entered the username and password that I set during step 5. When I clicked the Login button I got a message that read ... "The Publishing Engine user name or password is not valid." I tried stopping and restarting the following services: - FileMaker Publishing Engine (CWPE & CONFIG) - FileMaker Publishing Engine (WPC) - FileMaker Server 7 - FileMaker Server Helper ... still had same problem. I tried uninstalling then reinstalling: - FileMaker Server 7 - FileMaker Server 7 Advanced ... still had same problem. After that, I decided to poke around in the FileMaker program directory. I found several log files that may shed light on the problem if anyone can interpret them. Here's a description of what I found: ##[C:Program FilesFileMakerFileMaker Server 7Web Publishingjakarta-tomcatlogs]## STDERR.TXT - contains interesting error messages, here's a highly truncated summary of what I found: <summary> INFO: server has been restarted or reset this connection Feb 11, 2005 3:24:56 PM org.apache.jk.common.ChannelSocket processConnection SEVERE: Error, processing connection java.net.SocketException: Software caused connection abort: recv failed ........at java.net.SocketInputStream.socketRead0(Native Method) ........at java.net.SocketInputStream.read(Unknown Source) ........at java.io.BufferedInputStream.fill(Unknown Source) ........at java.io.BufferedInputStream.read1(Unknown Source) ........at java.io.BufferedInputStream.read(Unknown Source) ........at org.apache.jk.common.ChannelSocket.read(ChannelSocket.java:498) ........at org.apache.jk.common.ChannelSocket.receive(ChannelSocket.java:436) ........at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:551) ........at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:679) ........at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:619) ........at java.lang.Thread.run(Unknown Source) </summary> LOCALHOST_LOG.YYYY-MM-DD.TXT - contains java errors: <summary> javax.servlet.ServletException ----- Root Cause ----- javax.xml.transform.TransformerException Caused by: java.net.SocketException java.net.SocketException java.net.SocketException </summary> ##[C:Program FilesFileMakerFileMaker Server 7Web Publishinglogs]## WPC_ACCESS_LOG.TXT - contains the web console PASSWORD in PLAIN TEXT! WEB_SERVER_MODULE_LOG.TXT - contains interesting error messages <summary> jk_ws_service_t::start_response, ServerSupportFunction failed Error ajp_process_callback - start_response failed Error connecting to tomcat. Tomcat is probably not started or is listenning on the wrong port. Failed errno = 61 HttpExtensionProc error, service() failed ERROR: can't receive the response message from tomcat, network problems or tomcat is down. Error reading reply from tomcat. Tomcat is down or network problems. ERROR: Receiving from tomcat failed, recoverable operation. err=0 </summary> --------------------------------------------- Anyway, it looks like the problem has something to do with a corrupt xml file. Any ideas? logs.zip
infiniteg Posted February 11, 2005 Posted February 11, 2005 BTW.. There's an attachment to the previous post. It's a zip file that contains the log files I referenced.
infiniteg Posted February 11, 2005 Posted February 11, 2005 I found the solution to my problem in a post by Tyfud... Ok, fixed the problem. You have to uncheck "Integrated Windows Authentication" in IIS under directory security.
Salesman0Gil Posted March 21, 2005 Posted March 21, 2005 Just putting this here for the next person Step 1 On the Cisco Unity server, on the Windows Start menu, click Programs > Administrative Tools > Internet Services Manager. Step 2 Double-click <System-name> to expand it. Step 3 Under Default Web Site, right-click Web, and click Properties. Step 4 In the Properties dialog box, click the Directory Security tab. Step 5 Under Anonymous Access and Authentication Control, click Edit. Step 6 Check the Anonymous Access check box. Step 7 Uncheck the Integrated Windows Authentication check box. Step 8 Click OK to close the Authentication Methods dialog box. Step 9 Click OK to close the Default Web Site Properties dialog box. Step 10 Close the Internet Information Services window. --------------------------------------------------------------------------------
Salesman0Gil Posted March 21, 2005 Posted March 21, 2005 Just putting this here for the next person Step 1 On the Cisco Unity server, on the Windows Start menu, click Programs > Administrative Tools > Internet Services Manager. Step 2 Double-click <System-name> to expand it. Step 3 Under Default Web Site, right-click Web, and click Properties. Step 4 In the Properties dialog box, click the Directory Security tab. Step 5 Under Anonymous Access and Authentication Control, click Edit. Step 6 Check the Anonymous Access check box. Step 7 Uncheck the Integrated Windows Authentication check box. Step 8 Click OK to close the Authentication Methods dialog box. Step 9 Click OK to close the Default Web Site Properties dialog box. Step 10 Close the Internet Information Services window. --------------------------------------------------------------------------------
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now