[SOLVED] Developer Studio 7.7 installation on 32-bit Windows 7 system
Hi,
I am trying to install Developer Studio 7.7 on my local 32-bit Windows 7 system. After I installed, I checked the administration console verification tool and everything shows as "PASS". When I try to start the server OPSYS, it gave me an error
"(EDA13015) configuration error: 'admin_id' has no valid server administrator 10/19/2011 16:45:51.190 E You can register or update a server administrator by entering 'C:\ibi\DEVSTU~1\srv77\wfs\bin\edastart -change admin_id'"
Then I went to that path and did change the admin_id but that didn't solve the issue. But when I run the edastart from that path, the server looks like started but still not able to open the Developer Studio.
I am trying to find the following,
1) Did Developer Studio 7.7 need 64-bit system? 2) Do I have to install Webfocus server before installing Developer Studio 7.7? 3) If the above questions not the case, what am I doing wrong?
Thanks in advance,
regds KameshThis message has been edited. Last edited by: Kerry,
I use my own windows/lan id and password for that configuration.
quote:
1. Did Developer Studio 7.7 need 64-bit system?
I don't think Dev.Studio 7.7 is even available in a 64-bit version so the underlying system should not be a problem.
quote:
2. Do I have to install Webfocus server before installing Developer Studio 7.7?
If you're planning to install and use a full standalone Reporting Server in your local environment then yes, you should install that one before DevStudio. I personally find that unnecessary as Dev.Studio comes bundled with a Reporting Server anyway and everything I do in my "enterprise server" I can do with that one as well.
quote:
3) If the above questions not the case, what am I doing wrong?
Just verify your user credendials in edastart -change admin_id and try again.
I am using my network credentials. The interesting thing is, it is showing me the webfocus server console up to some extinct.
WFConsultant
WF 8105M on Win7/Tomcat
October 20, 2011, 11:35 AM
njsden
Take a look at edaprint.log for any messages that may give you a hint as to what is failing.
If you can start you server with security OFF and it works, then I would discard any installation problem and the whole issue would be surrounding security but I'm not sure exactly what. edaprint.log should help you find out why.