- •Table of Contents
- •1) Technical Support Specialist – Level 2
- •Qualification Requirements
- •2 ) Exceptions
- •3) Tier 2 Tools a) Solutions.24hourwebhostingsupport.Com
- •C) Linux Shell Commands
- •D) ipconfig
- •4) Absolute and Relative Paths a) Absolute Path
- •B) Relative Path
- •5) Possible Causes for Broken Sites
- •6) Installed Software:
- •7) Unix Services on the Hostopia Platform
- •A) cgi (Common Gateway Interface) faq
- •I.E. /services/webpages/h/o/hosting.Bluegenesis.Com/chat/chat.Log
- •B) Server Side Includes (ssi) faq
- •Can I use server-parsed image maps?
- •C) perl faq
- •How do I install and use Perl modules?
- •What is cpan?
- •What is supported by the jsp service?
- •What is a jsp file?
- •Where should my end users upload their jar files?
- •How do I Connect to an ms sql Database Source with .Jsp?
- •Upload appropriate libraries to your /public/web-inf/lib location
- •How do I Create a test .Jsp file?
- •Are there any potential issues ?
- •8) Windows® Services on the Hostopia Platform
- •A) Differences between Windows only Hosting and the Hybrid System
- •B) Functional Components
- •C) Non Functional Components
- •9) Asp 3.0 iis 6 (Active Server Pages)
- •A) asp Third Party Components
- •B) Server.MapPath()
- •C) The #include Directive
- •D) asp Coding Examples
- •1. Asp dsn connection for ms access
- •2. Asp dsn connection for MySql
- •3. Asp dsNless Connection for ms access
- •4. Asp dsnLess Connection To a MySql Database
- •5. Asp dsNless connection for ms sql
- •6. Defining Paths
- •7. AspMail Sample Code for Components
- •8. AspUpload Sample Code for Components
- •9. Cdonts Sample Code for Components
- •11. Sa Fileup Sample Code for Components
- •A) Features in asp.Net 2.0
- •B) asp.Net codebehind and Precompiled dll
- •C) Coding Considerations:
- •D) asp.Net codebehind and dll File Explanation
- •D) asp.Net ajax
- •E) Supported asp.Net File Extensions
- •F) Unsupported asp.Net file extensions:
- •G) Retrieving asp.Net Error Messages
- •H) asp.Net Coding Examples
- •11) ColdFusion 5 a) About ColdFusion 5
- •B) ColdFusion Applications
- •C) ColdFusion Tags
- •D) Supported ColdFusion Tags
- •E) Unsupported ColdFusion Tags
- •F) ColdFusion Error Messages
- •G) Custom ColdFusion Tags
- •H) ColdFusion Coding Examples
- •12) ColdFusion mx 7
- •13) Payment Gateways
- •13) Ssl (Secure Socket Layer)
- •A) Security Certificates
- •B) Common Issues with Installing a Custom ssl Certificate.
- •C) Creating Symbolic Links aka Symlink
- •Cd name_of_symlink
- •Rm name_of_link
- •Cd name_of_symlink
- •14) Databases a) ms access (Microsoft Access)
- •B) ms sql (Microsoft sql)
- •C) MySql
- •Import the dump.Sql file into a database:
- •15) Common Issues for Tier 2 a) Email
- •I. How to read Email Headers; Check for delays and Time Zone Discrepancies
- •II. How to Convert to utc (gmt)
- •1) Find the Time and Convert to utc!
- •2) Find the delay!
- •III. Bigfoot Mail System
- •IV. How to Test if the inbox is Corrupt
- •B) Formmail
- •2) Create a Test Form.
- •3) Copy and Paste Code into Form Non Secure Site
- •4) Verify that there is a cgi-bin.
- •6) Test the form. C) Sub Domains
- •D) Common Ports
- •E) Permissions
- •E) RealServer
- •F) EasySiteWizard 7
- •G) htaccess directives
- •H) Serrahost ProStores
- •I) FaxWire
- •J) Bell dns Remaps
C) Coding Considerations:
Customers are responsible for testing their code before moving to our systems.
The live environment should not be used for testing or making coding changes on a regular basis.
While coding, customers should be aware that files are not stored locally. All customer files are stored on a network share using dynamic paths.
Customers are advised not to hard code paths in their code, but to use Server.MapPath to point to their files. e.g C:\Inetpub\wwwroot\file.aspx, will not work.
Project files, i.e .sln, .csproj, .vbproj, vjsproj, .disco, .vsdisco and other files used for development, should be removed before uploading.
Dlls should only be places in the public/bin folder. If the customer wishes to run an application from a folder other than the public folder. A ticket can be submitted requesting the folder be converted to an application folder. The customer can then setup a bin folder within that folder and move dlls to that folder.
Why are my changes not showing up on my site?
Changes made to files and folders may not be visible immediately in ASP.NET. To maintain the performance of our servers we have disabled the file and folder monitoring feature of ASP.NET.
This prevents ASP.NET from constantly monitoring resources and recycling the application, which takes up system resources and causes session issues. In this case our support staff can recycle or change the recycle time for the customer. (default is 120 minutes)
Customers may notice a delay in the time from when they upload a new version of an existing filename. i.e., making modifications to their WebForm1.asax file, and overwriting the copy that exists within their web space. It may take up to 7 minutes before this new copy is processed by the .NET servers. This is due to an inherent behaviour of the .NET engine in which compiled assemblies aren’t destroyed and recreated quickly enough. ASP.NET differs from regular ASP on our systems in that we do not need to restart asp services when a modification to their Global.asax file is made.
Before uploading:
Customers are advised to make all changes in their development environment and then upload the final site to our servers.
The live environment should not be used for testing or making coding changes on a regular basis.
While testing, please check all visual studio debug logs, IIS logs and event viewer application logs. Any errors related to the site should be fixed before uploading. This will ensure a smooth transition to the live environment.
Security and performance:
Our servers and file systems are constantly being monitored. If any site is found trying to access restricted resources or if our system administrators suspect a site of degrading server performance. ASP.NET services for that site will be suspended and the customer will be notified.
Hostopia does not support coding issues, especially with dlls since they are compiled and the code cannot be viewed.
Customers are responsible for troubleshooting their code on a development system and providing our support staff with details of what their code is supposed to do. If the site is not performing according to their needs.