nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Worksite Web 8.0

mdiersma

Hi All,

Just installed the worksite on the same server as the rest of the package (for testing purposes)
And now im running into some problems. I do get the login page, but after i enter the login and password en press login....
the screen reloads.... i don't get the message that my credentials are incorrect.... it is simply reloading.

It is all running on a 2003 server with asp.net installed. The database is marked as web.
and the admin user is a member of the NRTADMIN group...

Can anybody help me ?

Regards,

Martijn Diersmann

Find more posts tagged with

Comments

Ben_inform

I have had heaps of pain with WSW 8 over the last 6 months..

In the end I uninstalled WSW hotfixes then WSW then ASP.net then deleted the worksite virtual web site then cleaned the registry then rebooted.

After that I installed WSW HF2

During the install I made WSW point to the IP of the DMS instead of the hostname (sometimes host name cause issues).
Also if your DMS is clustered this may add complications - just use one of the DMSs and its IP.
then restart.

Then make sure your browser does not cache pages and then it should be fine.

Migrateduser

For security reasons Worksite Web does not display the exact Error Message on Login Screen. However you could Turn of the "CustomeError" Modein web.config to see the Exact Error

There are couple of things to check when you see the blank screen
1) Make sure your DMS Server name is correct in web.config file
2) Make sure your bin\imanage.dll and bin]imanadmin.dll files are registered ( using regsvr32) Installer is suppose to register them but you should verify it in any case

3) On 2003 Make your your "Network Service" ( this is the account used by ASP.NET) has atleast read permission on \Worksite\Web folder and sub folders

4) If you still have issue then you should open a Ticket with Interwoven Worksite Tech Support

Thanks
Sheetal

mdiersma

Thanx for all the info. I managed to get it to work.
With the custom errors turned of, Asp.net said it hadn't access permissions to the folder.
When i resloved this, it worked perfectly.

Regards,

Martijn Diersmann