Unsolved
This post is more than 5 years old
17 Posts
0
1537
SourceOne Web Search
After fresh installation S1 7.1 SP2 we have for every login attempt to S1 web search: "Server unavailable. Login failed. Please try again".
All components of S1 are working fine (I think). We have one journaling policy which is correctly processing emails as we observe for example ExJBJournalexe.log
We have only Exchange 2010, and separated: one Master server, one Worker server, one Archive server, and one MS SQL server.
Where should I look for error trace of this problem?
RKatwal
600 Posts
1
September 9th, 2014 18:00
Greetings,
Journaling activities are independent of EMC SourceOne Web Search and Web Services. What you may want to check is that SourceOne Web Services installed properly followed by EMC SourceOne Web search component.
I would suggest following:
1. Make sure .net framework on SourceOne server where Web Services will be installed meets the requirements mentioned in the SourceOne Install guide.
2. Use the install files you used to install and run it for SourceOne Web Services first, that will prompt you for repair then perform the repair.
3. Reboot the server.
4. Use install file for SourceOne Web Search, that will also prompt you for the repair install, perform that.
5. In SourceOne MMC admin concole make sure Mapped folders have all the permissions set e.g. SourceOne Service account should have Admin and Read All permissions set.
6. Try to log in to web search using SourceOne Service account.
If you still have issue we may have to look at the verbose logs for Web Services and Web Search on the servers where it is installed.
Thanks,
Rajan
Tomsmi
17 Posts
0
September 11th, 2014 13:00
Thank you, I'll check those elements as you advised.
--
best regards,
Tom.
BenCs
114 Posts
1
September 18th, 2014 05:00
- Reboot Worker server(s)
- Make sure the Search and SearchWS site are visible in your IIS manager.
- Did you set SSO-properties?
- Have you enable the Query role to the Servers?
- Did it work in the past?
Tomsmi
17 Posts
0
September 21st, 2014 02:00
@katwar & @BenCs.
Thanky you guys. After investignation we suspect that problem was caused by duplicating computer accounts in AD.
Basically: three S1 VMs were created using clone of the same .vmdk disk, which was previously used in another production server registered in AD.
After ffresh install on new servers everything works fine.
Thanks for clues!
BenCs
114 Posts
0
September 23rd, 2014 02:00
Glad it solved your problem.