I follow the training step,
new a SSP application
set application folder (include setting applications publisher)
check the folder in /SSP applications
build a XXX.ssp in there. (used eclipse IDE, and upload it)
show up the XXX.ssp file --> used
http://shopping.na1.netsuite.com/c.TSTDRV0000000//XXX.ssp?n=1
but, still show up "page not found"
what did I miss?
You need to include the path to your ssp folder. It's not the file cabinet folder but the path you set up in the SSP Application definition.
e.g. http://shopping.na1.netsuite.com/c.TSTDRV0000000/path-to-ssp/XXX.ssp
Related
I created a web app on Azure. I am having issues adding additional html pages beyond an index. Is there something I'm missing? I've been searching to no avail.
Looks like you want to define your own start page name for the web app.
Files added to root path(aka wwwroot folder in kudu) can't be accessed with https://webappname.azurewebsites.net unless you set Default document in Application settings. Just add your file name in the list. The first matching file in the list is used.
If your page is deployed to a folder under root path, you also need to set Virtual applications and directories(also in Application settings). Change the physical path value from site\wwwroot to site\wwwroot\foldername.
I've created a new web site in IIS on my machine for testing purposes. Beneath the root I have a folder called documents where I have a bunch of pdf's that should be downloadable. However, when I hit the URL localhost:54510/documents/file.pdf I get a 404 error (Chrome, IE and Firefox).
I've added IIS_IUSRS permissions for the specified folders and the service is running since I can access my ASPNET WebApi - localhost:54510/api/whatever-service-function.
I can't grasp my head around what causes this.
PDF is specified in MIME-types as Application/pdf.
Another thing is, when I add the documents folder as a virtual directory in the Default web site then it works to download it from localhost:80/documents/file.pdf.
I have also tried to add the documents folder as a virtual directory in my web-site and set my local user as the authenticator to see if it had anything to do with permission.
I'm running on IIS 10.
Does anyone have any ideas?
I have a few fonts and a PDF file in the App_Data directory of my Web API project which is published to an Azure Mobile Service.
The build action is set to Content and I can see in the output window that the files are being published but when my code runs it cannot find the directory anywhere.
Assembly.GetExecutingAssembly().Location
Yields
"D:\\local\\Temporary ASP.NET Files\\root\\aea53938\\87de4b2f\\assembly\\dl3\\fb538bd2\\f38b146c_6ea3d001\\
Both of these
HostingEnvironment.ApplicationPhysicalPath
HostingEnvironment.MapPath("~/")
Yield
C:\\Program Files (x86)\\SiteExtensions\\MobileServicesDotNet\\1.0.450\\
If I do a Directory.GetFiles() and Directory.GetDirectories() using the directories above, none of them show an App_Data folder.
Where is this mystery folder located? Several Stackoverflow posts have suggested looking in bin\App_Data but it's not there either.
Try D:\home\site\wwwroot\App_Data
Make sure, that in VS Publish --> Settings the exclude option for App_Data is not set.
I have an InstallScript installer that utilizes dynamic file links for several components. These components contain configuration files that standard users should be able to edit. We recently discovered that when these files are installed on Windows Server 08, the permissions are set to full access for the Administrators group, but only read & execute access for the Users group. The typical install location is C:\programName.
I've tried creating new files manually as an admin (right click - new text file) in the C:\programName directory, and they are generated with identical permissions. I'm assuming that this is just the standard permission setup for new files.
Is there any way, within InstallShield, to set the permissions for dynamically linked files or the directory containing them?
I've looked for permission settings in
Organization -> Components
Application Data -> Files and Folders
but I haven't found anything. The documentation on dynamic file links makes no mention of permissions.
We are using InstallShield 2010.
Generally these permissions are a good thing; they're inherited from their parent folders. Non-administrator users (including the limited access admin before accepting a UAC prompt) should be unable to modify files under Program Files or C: so I would suggest addressing this concern in your application (for instance by using each user's Documents folder). Since you don't talk about why you need it, it's hard to say with certainty if this applies to your case.
If it turns out it does make sense to address this in the installation instead of the application, you can use the SetObjectPermissions API to set permissions programmatically.
In "Files and Folders" page right-click the file or folder, select Properties and click the Permissions button. In the "Permissions" dialog you can then right-click in the Name(s) list and use the New context menu option to add a new permission.
If the option is not available for a file, you can try setting it on the parent folder.
We've just moved our website to win2008 and IIS7 from win2000 with IS5 and I have some problems.
I have a folder that in it is an ASP page that upload a file to an upper folder, in the old IIS, I gave to the folder with the ASP page the permissions of the administrator and it's work fine, the files could be uploaded to an upper folders. BUT in the IIS7 I can't do it, I give to the folder with the asp code all the writing permission and it's not working. It's only work if I give a writing permissions to the upper targert folders. I don't wont to give to the target folders a full permission because those are the main web site folders.
So how can I do it? How can I give a folder a permission to write also to an upper folder that doesn's have this permmision?
Thanks
One possible reason is that you are attempting to access the parent with a MapPath and this is failing because Parent Paths haven't been enabled.
Since IIS6 the ability for code to access parent folders is by default blocked. To do this it is necessary to enable parent paths. In IIS7 parent paths can be enabled at Server, Site, Application or Folder level. In IIS manager click on the site, application or folder you want to enable this for, double click the ASP icon, in the Behavour section set 'Enable Parent Paths' to True.