SharePoint Foundation 2013 - Search Configuration Issue - 2 App Servers and 2 Front-End Servers

We have a SharePoint Foundation 2013 with SP1 Environment. 
In that, we have 2 Front-End Servers and 2 App Servers. In the Front-End Servers, the Search Service is stopped and is in Disabled state and in the 2 App Servers in One App Server, Search is Online and in another Search is Starting but goes to Stopped sooon
Originally, we had only 1 App Server and we were running our Search Service and Search Service Application in that. Now since the index location became full and we were unable to increase the drive there, we added one more App Server and now the issue is
Search is not properly getting configured in either of these App servers. What we want to do is run Search only in the new App Server, because we have a lot of storage space for Index locations here, but in the older App Server, not run Search at all.  We
tried keeping the Search Service disabled and ran the below PowerShell Scripts, but none of the ones are working. These scripts are creating the Search Service Application, but the error of "Admin Component is not Online", "Could not connect
to the machine hosting SharePoint 2013 admin component" is coming up.
Can I get some help please?
Karthick S

Hi Karthick,
For your issue, could you provide the
detail error message of ULS log  to determine the exact cause of the error?
For SharePoint 2013, by default, ULS log is at      
C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\LOGS
For troubleshooting your issue,  you can try to run the SharePoint Products Configuration Wizard on your WFE servers and run the script for configuring the search service on SharePoint
[string]$farmAcct = "DOMAIN\service_Account"
[string]$serviceAppName = "Search Service Application"
Function WriteLine
Write-Host -ForegroundColor White "--------------------------------------------------------------"
Function ActivateAndConfigureSearchService
# Based on this script :
Write-Host -ForegroundColor White " --> Configure the SharePoint Foundation Search Service -", $env:computername
Start-SPEnterpriseSearchServiceInstance $env:computername
Start-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance $env:computername
$appPool = Get-SPManagedAccount -Identity $farmAcct
New-SPServiceApplicationPool -Name SeachApplication_AppPool -Account $appPool -Verbose
$saAppPool = Get-SPServiceApplicationPool -Identity SeachApplication_AppPool
$svcPool = $saAppPool
$adminPool = $saAppPool
$searchServiceInstance = Get-SPEnterpriseSearchServiceInstance $env:computername
$searchService = $searchServiceInstance.Service
$bindings = @("InvokeMethod", "NonPublic", "Instance")
$types = @([string],
$values = @($serviceAppName,
$methodInfo = $searchService.GetType().GetMethod("CreateApplicationWithDefaultTopology", $bindings, $null, $types, $null)
$searchServiceApp = $methodInfo.Invoke($searchService, $values)
$searchProxy = New-SPEnterpriseSearchServiceApplicationProxy -Name "$serviceAppName - Proxy" -SearchApplication $searchServiceApp
catch [system.exception]
Write-Host -ForegroundColor Yellow " ->> Activate And Configure Search Service caught a system exception"
Write-Host -ForegroundColor Red "Exception Message:", $_.Exception.ToString()
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected].
Eric Tao
TechNet Community Support

Similar Messages

  • How can i configure Distributed cache servers and front-end servers for Streamlined topology in share point 2013??

    my question is regarding SharePoint 2013 Farm topology. if i want go with Streamlined topology and having (2 distribute cache and Rm servers+ 2 front-end servers+ 2 batch-processing servers+ cluster sql server) then how distributed servers will
    be connecting to front end servers? Can i use windows 2012 NLB feature? if i use NLB and then do i need to install NLB to all distributed servers and front-end servers and split-out services? What will be the configuration regarding my scenario.
    Thanks in Advanced!

    For the Distributed Cache servers, you simply make them farm members (like any other SharePoint servers) and turn on the Distributed Cache service (while making sure it is disabled on all other farm members). Then, validate no other services (except for
    the Foundation Web service due to ease of solution management) is enabled on the DC servers and no end user requests or crawl requests are being routed to the DC servers. You do not need/use NLB for DC.
    Trevor Seward
    Follow or contact me at...
    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

  • Sharepoint foundation 2013 Search Service Application.

    Hi all,
    I want to configure search application for sharepoint foundation 2013. I have followed some of the web links.
    But did not get success. Can you please provide me the working example of how to configure search application and run the crawl. And make sure the search is working correctly.
    Thanks  in advance for help.

    Hi Vishwajeet,
    According to your description, my understanding is that you want to configure SharePoint Foundation 2013 Search service application.
    In SharePoint Foundation 2013, we cannot add the Search Service to SharePoint Foundation 2013 from the Central Administration GUI after selecting a manual configuration method. It seems that the ONLY way you can add the Search Service to SharePoint Foundation
    2013 is by using the SharePoint Configuration Wizard.
    More information, please refer to the link:
    Best Regards,
    Forum Support
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Wendy Li
    TechNet Community Support

  • Sharepoint foundation 2013 search service crawl log

    Hi all,
    Whenever I try to open the crawl log in sharepoint foundation 2013 I am getting the following error. The error says nothing about the reason of failure to open the log.
    If just shows the co-relation ID in technical details.
    Correlation ID: d85cd49c-18f6-509e-ca23-13f39afa5192 (while trying to access the Crawl log)
    Correlation ID: e85bd49c-e836-509e-ca23-1a3f0ece8c28 (while trying to access the Content source)
    I searched a lot on the net but not able to find any solution to this.
    Can you please help me

    Can you please share details of this Correlation ID from ULS logs
    If this helped you resolve your issue, please mark it Answered. You can reach me through

  • Sharepoint Foundation 2013 User field issue

    Guys, I have an issue with Sharepoint Foundation 2013 site that we have created some custom workflows for. We have a couple required fields that we type in a users name and it automatically pulls up a user based on Active directory. once we choose that name
    and then save the form. the field immediately becomes blank when i open the workflow item back up. I'm kind of at a loss. I've already totally hosed the server once and was forced to restore.  This seams to have started when we installed share point server
    patch KB2881077 but i cannot uninstall or roll back the patch as there is no option to.

    If you're using SharePoint 2013 April 2013 CU or higher, this is a known issue where the People data is missing in Edit view. There is a separate issue that is resolved in the September 2014 CU:
    Consider the following scenario:
    You create a SharePoint 2013 list that contains a Person or Group (people picker) column.
    You create or edit an item, and then you select a person whose name contains a comma in the Person or Group field.
    In this scenario, the value of the Person or Group field is lost when you save the item. 
    Trevor Seward
    Follow or contact me at...
    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

  • Sharepoint foundation 2013 "The trust relationship between this workstation and the primary domain failed"

    Hi Sir/Madam,
    I try to connect the sharepoint foundation 2013 server by remote desktop recently using domain account, but it show the error message that mentioned in the subject. I can login the server using local account. Do I need to disjoin
    the domain then rejoin the domain? Will there be any risk if I do this? 
    My SharePoint environment as below:
    Primary domain : abc.local (DC : windows server 2012 standard R2)
    SharePoint : SharePoint foundation 2013 and SQL Standard 2012 installed on a single windows server 2012 standard (not R2, joined domain "abc.local)
    I tried this on DC > active directory user and compouter >right click Sharepoint pc > click reset > reboot sharepoint server, reboot sharepoint server but still cannot login using AD account
    I also tried netdom command and powershell command "Reset -ComputerMachinePassword" also failed to reset the password.
    Please help to resolve my problem. Thanks

    Go to Control Panel -> System -> under Computer Name, Domain, click Change Settings. Click on the Change button, then re-type the domain in the NetBIOS or FQDN format, which ever it is currently not set to. This will force a soft-join to the domain.
    Trevor Seward
    Follow or contact me at...
    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

  • Search on App and Front End servers

    Hi, we migrating from SharePoint 2010 to SharePoint 2013. And I have a question for Search Service Application.
    On SharePoint 2010 Search application we have Crawl hosted on APP server and index partitions hosted on Front-end servers.
    On SharePoint 2013 Search application in Search Application Topology I see only App server with all components marked as OK.
    Is it enough to have only one App server in Search Application Topology. Or should I add Front-end server to Search Application Topology too?

    For a good user experience and performance, it is recommend that WFE servers hold Query processing component, App servers hold Analytics processing component,Content processing component,Crawl component,Search administration component. Here is the PowerShell
    Script for Configuring Enterprise Search Topology:
    $hostWFE = Get-SPEnterpriseSearchServiceInstance -Identity "sp"
    $hostApp = Get-SPEnterpriseSearchServiceInstance -Identity "app"
    Start-SPEnterpriseSearchServiceInstance -Identity $hostWFE
    Start-SPEnterpriseSearchServiceInstance -Identity $hostApp
    Get-SPEnterpriseSearchServiceInstance -Identity $hostWFE
    Get-SPEnterpriseSearchServiceInstance -Identity $hostApp
    $ssa = Get-SPEnterpriseSearchServiceApplication
    $newTopology = New-SPEnterpriseSearchTopology -SearchApplication $ssa
    New-SPEnterpriseSearchAdminComponent -SearchTopology $newTopology -SearchServiceInstance $hostApp
    New-SPEnterpriseSearchCrawlComponent -SearchTopology $newTopology -SearchServiceInstance $hostApp
    New-SPEnterpriseSearchContentProcessingComponent -SearchTopology $newTopology -SearchServiceInstance $hostApp
    New-SPEnterpriseSearchAnalyticsProcessingComponent -SearchTopology $newTopology -SearchServiceInstance $hostApp
    New-SPEnterpriseSearchIndexComponent -SearchTopology $newTopology -SearchServiceInstance $hostApp -IndexPartition 0
    New-SPEnterpriseSearchQueryProcessingComponent -SearchTopology $newTopology -SearchServiceInstance $hostWFE
    Set-SPEnterpriseSearchTopology -Identity $newTopology
    For more information,you can refer to the articles:
    Best Regards,
    Eric Tao
    TechNet Community Support

  • Team Foundation Server 2013 with SharePoint Foundation 2013 - Search not available?

    we installed a TFS 2013  and let it deploy SharePoint Foundation on the same server. We are now faced with the fact that search in the teamsites is not working. I tried to get that search service up and running in a number of ways but it appears
    as if there's no search service at all.
    I have seen all the blogs where people are explaining how to provision a search service application for SharePoint Foundation but none of these ways work.
    So, my question... is it possible to get it working?
    PS. Please don't advice to post this on the TFS forum... I'm coming from there. They just closed my question as answered with the advice to post it in the SharePoint forum.

    When you go to the Search Settings in the Site Actions menu of a site, a message is displayed that there's no search Service. Which is kind of normal since there's no Search Service Application provisioned.
    When I go to Central Administration => Services on Server => There's no Search Service.
    When I go to Central Administration and I run the configuration wizard, there's no search service application to be provisioned.
    There's a Search Administration section in the General Settings but it only displays the upper section. The lower section (with the Search Service Application information) just gives me nothing. An animated loading icon.
    I tried to provision the services with psconfig (psconfig -cmd services -install) but there's still no search service to be found anywhere. After this, I do have a Search Host Controller service but when I try to start it in Central Administration, it just
    gives me an error.
    I'm starting to think it's not a full SharePount Foundation which is shipped with TFS.
    The only thing we want to achieve is that a user can search for a document he uploads in a team site which is created by TFS. Seems not possible... unless I'm missing something here.

  • SharePoint foundation 2013 Search is not working

    Hi, Search was working 3 days back, but today its not working. So
    1. I Recreated Search Service Application
    2. Created Content Source and set full crawl.
    3. And service application is associated to the web application also.
    4. All Application pool id are running.
    5. Created Search Site collection, even though search is not working.
    The error message i got was shown below. How to resolve this issue. An help/thoughts.

    Try to use word Home in search
    Do we see site getting crawl in crawl logs
     Navigate to the site for which you want to control the Web Parts in search results.
    Click Site Actions, and then click Site Settings.
    Under Site Administration, click Search and offline availability.
    In the Indexing ASPX Page Content section, under
    This site does not contain fine-grained permissions. Specify the site’s ASPX page indexing behavior , 
    Always index all Web Parts on this site

  • SharePoint Foundation 2013 search service crawl error

    Hi all,
    When I try to view the Crawl log of Search Service Application I am getting error something like below:-
    I tried to figure out why this is happening but could not find the error details related to above Correlation ID.
    Can you please help me & guide me in right direction. I am clueless how to fix this issue. Yesterday it was working  fine but somehow it stopped working today and it even does not display the Crawl log. So it has become tough at least for me to
    fix it.
    Thanks for help.

    Did you try a using the
    Merge-SPLogFile cmdlet to retrieve the events that use this correlation ID?
    Merge-SPLogFile -Path ".\example.log" -Correlation "0467d49c-c872-509e-ca23-16445ea822d4"
    You can also check out my blog post, An even better way to get the real SharePoint error from the ULS logs which describes the
    process for using Merge-SPLogFile
    Jason Warren

  • Disappearing Sharepoint Foundation 2013 anonymous list submissions

    I have a custom Sharepoint Foundation 2013 list configured to allow anonymous submissions from a public facing website, but which requires admin permissions to view the full list content. Think like a contact form or an online application - anonymous users
    can submit a new item via the form, but get "permission denied" when attempting to access the list itself. I've customized the New Item .aspx in Sharepoint Designer, and I've also added a redirect page after submission for a "confirmation"
    This seems to work perfectly in all of my tests - but I have several dozen users who have reported correctly filling out the form, pressing "Submit," and being taken to the confirmation page, but the list item is nowhere to be found when I log in
    and look at the list. It appears that somehow Sharepoint is losing the new list item, while still redirecting users to the post-submission confirmation page.
    If it was a single user, I'd chalk it up to user error (not pressing Submit or something), but I have enough identical reports to verify that this is definitely happening and data is definitely being lost. I have similar reports from users of all 3 major browsers,
    both Mac and PC. 
    Unfortunately, I can't reproduce this behavior on demand - the form works fine for me no matter what I throw at it. There's nothing in the recycle bin, no validation errors (I've turned off all validation for the form), and I have tried every browser/OS combination
    I can think of. In every single test I have done, the form submits flawlessly, and the new list item appears immediately - even for a blank form.
    Any ideas? Where do I even start trying to troubleshoot this if it happens seemingly at random?
    Thanks in advance for any thoughts...

    Without being able to reproduce the problem I can imagine this will be a difficult one to diagnose. I would start by getting some dates and times from users from when they did submit items that they are claiming did not appear in the list. I would then look
    in the ULS logs around these times and see if you can see the item being submitted / created.
    Brian Jones

  • Users in new OU in Active Directory have to enter credentials when accessing SharePoint Foundation 2013

    We have a SharePoint farm consisting of one web front end server and one database server, running SharePoint Foundation 2013.  This farm has been up and running for over a year and uses AD for authentication, and SharePoint groups for authorization.
    The problem we are seeing is when we create a new Organizational Unit in AD, and add users under this new OU they are prompted for their credentials when trying to access SharePoint.  We've done the below tests to narrow the issue down:
    1) New user (xxx) in new OU (111) logs into Windows PC and tries to access SharePoint via IE 10 -- they are prompted for their credentials. They are required to enter their username as 'domain\username' to be able to log in successfully to SharePoint.
    2) Existing user (yyy), in existing OU (222) logs into same Windows PC and tries to access SharePoint via IE 10 -- they are NOT prompted for their credentials and get into SharePoint successfully.
    3) Existing user (yyy) is moved into new OU (111), logs into same Windows PC and tries to access SharePoint via IE 10 -- they are prompted for credentials and need to use 'domain\username' to log in to SharePoint
    4) Existing user (yyy) is moved out of new OU (111) and back into their old OU (222), logs into same Windows PC and tries to access SharePoint via IE 10 -- they are prompted for credentials and need to use 'domain\username' to log in to SharePoint
    Note: both the new OU (111) and old OU (222) are within the same parent OU.
    1 & 2 combined tell me that it's not a PC or IE issue. We've also tried 1 & 2 on multiple PCs so that would eliminate a profile issue as well.
    To me it seems that SharePoint doesn't know that the new OU is in our domain, so it doesn't think the users within the new OU are in our domain, which is why they have to supply the domain with their username when logging in...but I'm not exactly an expert
    when it comes to AD so this is just a guess on my part.
    As a long shot, what I thought may fix it would be by syncing AD with SharePoint by using User Profile Synchronization, but it's not offered as part of SharePoint Foundation, so I used this nice solution at CodePlex (,
    but that did not fix it.
    Does anyone have any ideas on how to fix this?  Or what the issue may be?

    Hi Christopher,
    Thanks for the reply.
    I feel very stupid right now -- I did look at this before posting this question to the forum, but it seems I didn't look far enough. 
    We have a GPO that enters our domain into the 'Local intranet' of IE.  Our SharePoint site's URL is "" and we've got "*" under Local intranet sites.  But, I also found the FQDN ""
    under 'Trusted sites' and that seems to confuse SharePoint because once I moved the FQDN to Local intranet, and removed it from Trusted Sites, the user is now not prompted for their credentials when going into SharePoint.
    Thanks for your reply in making me take a second look.
    EDIT: We've just removed the FQDN from Local intranet, so all we have is "*" under Local intranet and it works as well.

  • SharePoint 2007 (WSS 3.0) migration to SharePoint Foundation 2013

    I have a requirement to migrate a SharePoint 2007 (WSS 3.0) farm to a SharePoint Foundation 2013 farm. The WSS 3.0 farm has SQL Server 2005 Standard running so no restrictions on the size of the content database. The SharePoint Foundation 2010 and 2013 farms
    will share the same SQL Server 2012 Standard instance (as I know WSS 3.0 will have to be migrated to 2010 before 2013). I also have two other WSS 3.0 farms (so three WSS 3.0 Farms, lets call these A (250GB), B (90GB) and C (60GB)) that I need to migrate
    into WSS 3.0 Farm A before the migration to SP 2010.
    My question is, can I migrate a 400GB WSS 3.0 site collection to SP 2010 or will I have to split this into separate site collections? I have read that there is a best practice limit of 100GB per site collection but this does not stop a larger migration from
    happening. Obviously over time when the migration has completed to SharePoint Foundation 2013 the single site collection will grow and grow so perhaps now is the right time to split this out into, say, year named site collections, but surely this will incur
    an end of year process to create new site collections and a custom dev headache due to different locations to send newly created sites?

    The answer is Yes, and you are correct about the best practice of a limit of 100GB,
    although, document and record centers (e.g. non collaborative) can go much higher.
    That being what it is, your sites will perform better if you find a topology that allows the content databases to be under 100GB each.  You can use Move-SPSite to accomplish that feat.
    You'll want a separate instance for 2010 and a separate instance for 2013
    and finally, put some quota's in place and then governance document\statement that informs users that 100 GB is the max for any given site collection that uses collaborative features (calendars, lists, workflows, etc.)
    The simple path is explained on technet, go from 2007 to 2010 (you can inplace upgrade if you want) then go from 2010 to 2013, database detach and attach is only way.
    please check the below link that explains more about the migration from share point 2007->2013.

  • Sharepoint Foundation 2013 Configure Search Navigation

    I am testing out the search feature of Foundation 2013 and I want to allow my users to refine their searches via Result Sources.  From the instructions that I have read I should be able to do this in the Global Search Results page that I created ->
    Site Settings -> Search -> Search Settings.  It appears there should be a section for "Configure Search Navigation".  I do not have this option.  Is this something that is disabled in the Foundation edition of Sharepoint?
    For reference here is what I was following for instructions. About halfway down the page it shows this configuration box.  I cannot see that on my Search Settings page at all.
    I have successfully created a Result Source that does work, but I seemingly have no way of presenting that to the user.  The Navigation WebPart also relies on the "Configure Search Navigation" settings, which I can't see in my setup.

    "Configure Search Navigation" is not present in SharePoint Foundation 2013, but it is still available
    via SOM (and PowerShell, of course). Try this if this helps (full url of Search Center on my dev environment is http://dev/search):
    using (var siteCollection = new SPSite("http://dev"))
    using (var site = siteCollection.OpenWeb("search"))
            new SPNavigationNode("Test", "http://dev"));

  • SharePoint server 2013 Search Service App on Windows server 2012 R2 not working

    Hi all,
    I installed SharePoint server 2013 on Windows  server 2012 R2 using VirtualBox.  I created a DC(domain controller) server with a domain set up on one VM and it has SQL server 2012 SP1 installed. Then SharePoint 2013 on another VM
    was set up to access the DC server.  Everything seems working except Search Service App which cannot be sucessfully set up. Creation process for Search service app says Successful and 4 search databases were created and look fine. But when I navigate
    to search service app admin page, it gives error info:
    System status:  The search service is not able to connect to the machine that hosts the administration component. Verify that the administration component '386f2cd6-47ca-4b3a-aeb5-d9116772ef16' in search application 'Search Service Application 1' is
    in a good state and try again.
    Search Application Topology:  Unable to retrieve topology component health states. This may be because the admin component is not up and running.
    From event viewer, I see following errors:
    (1) Error From source: SharePoint Server
    Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (b7c72eb8-cbaf-435e-b4c9-963cb6e4e745).
    Reason: The object you are trying to create already exists. Try again using a different name. 
    Technical Support Details:
    System.Runtime.InteropServices.COMException (0x80040D02): The object you are trying to create already exists. Try again using a different name. 
       at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()
       at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)
    (2) Error From source: SharePoint Server Search
    Could not access the Search database. A generic error occurred while trying to access the database to obtain the schema version info.
    Context: Application '386f2cd6-47ca-4b3a-aeb5-d9116772ef16'
    (3) Warning from source: SharePoint Server Search
    A database error occurred. Source: .Net SqlClient Data Provider Code: 8169 occurred 0 time(s) Description:  Error ordinal: 1 Message: Conversion failed when converting from a character string to uniqueidentifier., Class: 16, Number: 8169, State: 2   
    at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
    (4) Error From source: SharePoint Server
    Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (b7c72eb8-cbaf-435e-b4c9-963cb6e4e745).
    Reason: The gatherer application could not be mounted because the search administration database schema version does not match the expected backwards compatibility schema version. The database might not have been upgraded. 
    Technical Support Details:
    System.Runtime.InteropServices.COMException (0xC0041235): The gatherer application could not be mounted because the search administration database schema version does not match the expected backwards compatibility schema version. The database might not have
    been upgraded. 
    Since separate DC server and SharePoint server do not work, I installed SharePoint 2013 on DC server ( so DC server has everything on it now ) but it gives exactly same result. Later I installed SharePoint 2013 SP1 and still have the same problem
    with Search Service app. I spent two weeks tried all suggestions available from Web and Google but SharePoint Search Service simply does not work. Config and other databases work but why Search Service has this issue seemingly related to search DB.
    Could anybody please help out? You deserve a top SharePoint consultant award if you could find a solution. I am so frustrated and so tired by this issue.    
    Thanks a lot.

    According to your post, my understanding is that  SharePoint server 2013 Search Service App did not work on Windows server 2012 R2.
    Please make sure you configure Search Service Application correctly. You can refer to:Create and configure a Search service application in SharePoint Server 2013
    I recommend to created new Search Service Application, and made a full crawl. Then assigned the new SSA as the default SSA for webapplications. Finnlay checked  the issue doesnt occur now,
    If all search related components now are online, to keep the enviroonment clean, you can delete the old SSA.
    Thank you for your understanding.
    Best Regards,
    Linda Li
    Linda Li
    TechNet Community Support

Maybe you are looking for

  • 10.5.8 Finder resets to default, desktop files gone!

    The Finder on my 2008 Mac pro is really acting up at the moment an I have no idea what's going on. My desktop has been wiped clean. Nothing there, except the drive icons. I don't keep much on the desktop but there should be a few folders and files th

  • Steps to load the data by using flat file for hierarchies in BI 7.0

    Hi Gurus, steps to load the data by using flat file for hierarchies in BI 7.0

  • The Exchange Rate in Commitment Managment

    Now in our system, the commitment check for PR/PO (table COOI) , the the foreign amount to local amount is based on M rate. Is it possible to changed by other exchange rate type?  If yes, how to do it? Thanks a lot.

  • Photos visible in iPhoto application but not accessible for upload

    Any help anyone can provide with this is greatly appreciated. I took pictures of a friends wedding and have been trying to order a photobook as a gift. I decided to try to use iPhoto to make the book. I don't use iPhoto very often and at the start of

  • PLD Text Fields in Collection Report

    Can someone please tell me how the data is populated for the Repetative Area() of the Collection Report? When I look at the System Collection Report all of the fields in the Repitive Area() are listed as Free Text.  I'm looking to modify/add some fie