Document number | Revision |
---|---|
DOCU12216 | 1 |
Frequently Asked Questions (Administrator)Why does user not have access to web site?How can auto FolderType be set to MS Network for users running Windows/IE?How do we make FolderType and FolderView visible to basic users?How can we set default FolderView to list+autofolder?How to convert to Unicode UTF-8 encoding?How to avoid linked server and performance penalty by linked server?How make authentication work for local (on server) requests to website?Some file types are not accessible through http, how do we allow download of specific file types?To satisfy regulatory requirements, how do we restrict document search to latest approved version only?How do we remove the ftp value from FolderType values?When running HS/TS fusion, how do we redirect action/ document/ part links to Highstage?How can crawl search be called with parameter to specify specific types to be searched?How to change color theme?How do I set different schema variants for different servers?Why does the new generation (TurboStage) show slower execution time on web pages?Why will large files not upload to server through WebDAV ?
Refer to trouble shooting section in Active Directory (Ldap) usergroup and user replication.
This can be done by setting the parameter IeAutoFolderType in web.config file. The parameter must be set to the numeric equivalent of the desired folder type:
<add key="IeAutoFolderType" value="5"/>
By default these fields are just available to advanced users. To make them visible to basic users include the following schema xml snippet:
xxxxxxxxxx
<type name="ts_role">
<column name="FolderType" read="everyone" />
<column name="FolderView" read="everyone" />
</type>
By setting column FolderView default value to ‘1’. Include the following schema xml snippet and run the page System/Schema/Apply.aspx:
xxxxxxxxxx
<type name="ts_role">
<column name="FolderView" sqldefault="1" />
</type>
Also existing users must have FolderView column set to ‘1’ either through web interface or by sql update: UPDATE ts_role SET FolderView=1
web.config must have:
xxxxxxxxxx
<globalization requestEncoding="UTF-8" responseEncoding="UTF-8" />
Convert database column from varchar to nvarchar in both database and schema.
Create a new connection string in web.config, in the following sample it has the name finance:
xxxxxxxxxx
<connectionStrings>
<add name="default" … />
<add name="erp" … />
</connectionStrings>
Use the connection attribute on the type (s) you want to use the new connection:
xxxxxxxxxx
<type name="axapta:prodtable" connection="erp" />
Symptom is when you use the fully qualified domain name (FQDN) or a custom host header to browse a local Web site that is hosted on a computer that is running Microsoft Internet Information Services (IIS) 5.1 or a later version, you may receive an error message that resembles the following:
HTTP 401.1 - Unauthorized: Logon Failed
This issue occurs when the Web site uses Integrated Authentication and has a name that is mapped to the local loopback address.
Note! You only receive this error message if you try to browse the Web site directly on the server. If you browse the Web site from a client computer, the Web site works as expected.
Microsoft provides the following solution: http://support.microsoft.com/default.aspx?scid=kb;en-us;896861
Here is a short version of the recommended setup:
Step 1: Set the DisableStrictNameChecking registry entry to 1.
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters
Value name: DisableStrictNameChecking
Data type: REG_DWORD
Radix: Decimal
Value: 1
Step 2: Specify host names
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0
For Windows 2003 servers also consult this page: http://support.microsoft.com/kb/957097/
By default web server allows download of a number of file types. To allow a new file type to be downloaded a MIME type must be setup at the web server. The following IIS7 web.config sample shows how to enable FreeMind file type:
xxxxxxxxxx
<system.webServer>
<staticContent>
<mimeMap fileExtension=".mm" mimeType="application/freemind" />
</staticContent>
</system.webServer>
By including the following schema snippet:
xxxxxxxxxx
<type name="doc" filter="latestapproved" />
By including the following schema snippet:
xxxxxxxxxx
<type name="ts_role" >
<column name="foldertype">
<values name=".">
<value name="ftp" _delete="1" />
</values>
</column>
</type>
Search should be done in TS but the actual viewing and work on an item will be done in HS. Include the following schema snippet:
xxxxxxxxxx
<type name="ts_item" url="/item/item.aspx?ot=@[t]&o=" />
Sample 1:
This sample URL searches documents and parts for the text “test”:
../../crawl.aspx?t=doc;action&_text=test
Sample 2:
This sample URL searches document raw grid for the text “test”. It is important that ’&’ char is URL escaped to %26, .NET contains support for URL escaping, it is important that only parameters are URL escaped and not the entire URL:
../../crawl.aspx?t=doc%26_grid=raw&_text=test
Three different base colors themes are provided:
Default color theme is ts/css/white. To change color theme put one of the following schema snippet lines in custom.schema.xml:
xxxxxxxxxx
<css name="ts_color" src="ts/css/black.css" />
<css name="ts_color" src="ts/css/gray.css" />
If you have different servers with different colors but wants to use the same custom.schema.xml file for all servers, you may use a parameter defined in web.config file:
Web.config:
xxxxxxxxxx
<add key="CssFile" value="ts/css/black.css" />
Custom.schema.xml:
xxxxxxxxxx
<css name="ts_color" src="parameter:CssFile" />
A different approach is to use the SchemaFile parameter to set different schema variants for different servers.
Suppose you have a “production” server and a test server. You want to use same schema except for small variants on the test server.
On the test server you may specify a different schema file for example testserver.schema.xml which includes the custom.schema.xml file. After the include you may make changes to the schema that only applies to test server, in this sample we change color theme to black:
xxxxxxxxxx
<schema>
<include src="custom.schema.xml" />
<css name="ts_color" src="ts/css/black.css" />
</schema>
Basically the following reasons:
You may improve execution time by removing information from web pages. But this is probably not what your customers (users) want. For example to remove display of references in linked data section use the following schema snippet:
xxxxxxxxxx
<type name="ts_item" types=""/>
Still the system is pretty fast. Except for more information retrieved from SQL server the Web Server is now more loaded, but the web server is relatively easy to scale in opposition to a real-time SQL server which will for sure be the main bottleneck even in the future.
In IIS/ASP.NET WebDAV server you must specify the file maximum upload size in web.config of your web application. By default maximum upload size is set to 4096 KB (4 MB) by ASP.NET. To increase the upload limit add appropriate section to your web.config file and specify the limit.
In case of IIS 7.x, both Integrated and Classic mode:
xxxxxxxxxx
<system.webServer>
<security>
<requestFiltering>
<requestLimits maxAllowedContentLength="2147483648" />
</requestFiltering>
</security>
</system.webServer>
In case of IIS 6.0:
xxxxxxxxxx
<system.web>
<httpRuntime maxRequestLength="2097151" />
</system.web>
The maximum file upload size for both ASP.NET 2.0 and ASP.NET 4.0 is 2097151Kb = 2Gb.