|
Q1
|
Why won't my project deploy properly?
|
|
A1
|
When you work with Magic xpi as a service, you should not use mapped network drives. This is to prevent problems that might occur at the project deployment stage, where a customer is unlikely to be using the same mapped network drives as a developer. Read-only files cannot be processed.
|
|
|
|
|
Q2
|
What should I do if I receive a "Failed to create project's .ecf file" error when attempting to build a project using Build or Build-all?
|
|
A2
|
Verify that the LicenseName flag in the ifs.ini file points to a valid license. For example, IBNPSRV.
|
|
|
|
|
Q3
|
How can I extract a deployment package at a target Server machine?
|
|
A3
|
Copy and paste the package's zip file from the Magic xpi Studio machine to the target Server machine (under the Magic xpi installation's root folder).
Then extract the zip file with any external zip tool.
|
|
|
|
|
Q4
|
Why does my project shut down after 24 hours?
|
|
A4
|
When you deploy a project, you must use a production license. If you are using a non-production license, the project will shut down after 24 hours.
|
|
|
|
|
Q5
|
Only my first project is running. All of my other projects are shutting down. Why is this?
|
|
A5
|
A possible cause is that this project started with MaxConcurrentRequests = 0, which means that this project consumed all the license threads. This is the default in the Magic.ini file.
|
