This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Error while attempting search in/ below folder
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 17, 2009
10:08 AM
Error while attempting search in/ below folder
I am getting the following error in my log while system search is running:
MSI (c) (74:C4) [15:00:57:462]: Note: 1: 2363 2: C:\Program Files\Microsoft SQL Server\MSRS10.MSSQLSERVER\Reporting Services\
MSI (c) (74:C4) [15:00:57:462]: Error while attempting to search in/ below folder: Reporting Services
Actually, it occurs quite a few times. Any info on why this would occur?
Consequently it isn't finding the file on the machine even tough it does exist.
BOb
MSI (c) (74:C4) [15:00:57:462]: Note: 1: 2363 2: C:\Program Files\Microsoft SQL Server\MSRS10.MSSQLSERVER\Reporting Services\
MSI (c) (74:C4) [15:00:57:462]: Error while attempting to search in/ below folder: Reporting Services
Actually, it occurs quite a few times. Any info on why this would occur?
Consequently it isn't finding the file on the machine even tough it does exist.
BOb
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 17, 2009
11:49 AM
Are there any unusual permissions on that directory? I see that 2363 error with (for example) a two-deep search starting on [WindowsVolume], for C:\System Volume Information\, C:\preboot\, and other system folders...
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 18, 2009
10:35 AM
Robert,
It appears it was a permissions issue. When we forced it to run "As Administrator" it worked.
I had failed to set the required execution level to "Administrator" so the Win 2008 os what not elevating to full admin. I hope this change fixes it. We are testing now.
Thanks for the help.
BOb
It appears it was a permissions issue. When we forced it to run "As Administrator" it worked.
I had failed to set the required execution level to "Administrator" so the Win 2008 os what not elevating to full admin. I hope this change fixes it. We are testing now.
Thanks for the help.
BOb
