Server error compiling big documents, ShareLatex
I am trying to compile a large document with several chapters in ShareLatex. Each Chapter compiles correctly with minor (often unavoidable) errors but when I try to compile more than 2 chapters together I get the following error: Server error, Sorry, something went wrong and your project could not be compiled. Please try again in a few moments. Trying again later does nothing to rectify the issue. This is in draft mode as well so images are not the issue.
EDIT: MWE included
documentclass[12pt, twoside]{report}
usepackage[utf8]{inputenc}
setlength{parindent}{0pt}
usepackage{parskip}
usepackage{setspace}
usepackage{array}
doublespacing
usepackage[a4paper, left=40mm, top=25mm, right=20mm, bottom=25mm]{geometry}
usepackage{graphicx}
graphicspath{{Images/}{../Images/}}
usepackage[outdir=./]{epstopdf}
usepackage{tabularx}
usepackage{multirow}
usepackage{arydshln}
renewcommand{arraystretch}{1.5}
usepackage{rotating}
usepackage{makecell}
usepackage[justification=justified]{caption}
usepackage{comment}
usepackage{fancyhdr}
pagestyle{fancy}
fancyhead{}
fancyhead[C]{Chapter thechapter}
setlength{headheight}{14.5pt}
fancyfoot{}
fancyfoot[RO,LE]{thepage}
usepackage[version=4]{mhchem} %for equations
usepackage{chemnum}
usepackage{xparse}
NewDocumentCommand{cecount}{ O{#2} m }{ce{#2} (cmpd{#1})}
usepackage{etoolbox,calc}
makeatletter
pretocmd{@makechapterhead}{setcounter{cmpdmain}{100*thechapter-1}}{}{}
makeatother
usepackage[journal = angew]{chemstyle}
cstsetup{radhyphen = false,radsuper = true,abbremph = true}
usepackage{chemscheme}
usepackage{siunitx}
usepackage[backend = biber, style=chem-angew]{biblatex}
addbibresource{mendeley.bib}
begin{document}
chapter{Introduction}
input{Chapters/chapter1.tex}
input{Chapters/chapter2.tex}
etc...
sharelatex compilation-error
|
show 4 more comments
I am trying to compile a large document with several chapters in ShareLatex. Each Chapter compiles correctly with minor (often unavoidable) errors but when I try to compile more than 2 chapters together I get the following error: Server error, Sorry, something went wrong and your project could not be compiled. Please try again in a few moments. Trying again later does nothing to rectify the issue. This is in draft mode as well so images are not the issue.
EDIT: MWE included
documentclass[12pt, twoside]{report}
usepackage[utf8]{inputenc}
setlength{parindent}{0pt}
usepackage{parskip}
usepackage{setspace}
usepackage{array}
doublespacing
usepackage[a4paper, left=40mm, top=25mm, right=20mm, bottom=25mm]{geometry}
usepackage{graphicx}
graphicspath{{Images/}{../Images/}}
usepackage[outdir=./]{epstopdf}
usepackage{tabularx}
usepackage{multirow}
usepackage{arydshln}
renewcommand{arraystretch}{1.5}
usepackage{rotating}
usepackage{makecell}
usepackage[justification=justified]{caption}
usepackage{comment}
usepackage{fancyhdr}
pagestyle{fancy}
fancyhead{}
fancyhead[C]{Chapter thechapter}
setlength{headheight}{14.5pt}
fancyfoot{}
fancyfoot[RO,LE]{thepage}
usepackage[version=4]{mhchem} %for equations
usepackage{chemnum}
usepackage{xparse}
NewDocumentCommand{cecount}{ O{#2} m }{ce{#2} (cmpd{#1})}
usepackage{etoolbox,calc}
makeatletter
pretocmd{@makechapterhead}{setcounter{cmpdmain}{100*thechapter-1}}{}{}
makeatother
usepackage[journal = angew]{chemstyle}
cstsetup{radhyphen = false,radsuper = true,abbremph = true}
usepackage{chemscheme}
usepackage{siunitx}
usepackage[backend = biber, style=chem-angew]{biblatex}
addbibresource{mendeley.bib}
begin{document}
chapter{Introduction}
input{Chapters/chapter1.tex}
input{Chapters/chapter2.tex}
etc...
sharelatex compilation-error
1
Everything will remain pure speculation unless you don't provide a Minimal Working Example.
– AlexG
Aug 30 '18 at 13:35
1
What happens when you compile locally?
– Jeffrey J Weimer
Aug 30 '18 at 13:37
1
I am trying to compile locally now to see if that works, thanks for the suggestion. MWE added above
– Tmr90
Aug 30 '18 at 13:55
1
It will compile locally but my references (biblatex) are now not working and the headers and footers and page numbers are messed up!
– Tmr90
Aug 30 '18 at 14:05
1
The commentcompiles correctly with minor (often unavoidable) errors
is very suspicious, no tex errors are unavoidable, and given tex's error recovery strategies I would never use any pdf generated by a tex run that makes any error. But you have not said what errors you get or given any other indication of the problem.
– David Carlisle
Aug 30 '18 at 16:50
|
show 4 more comments
I am trying to compile a large document with several chapters in ShareLatex. Each Chapter compiles correctly with minor (often unavoidable) errors but when I try to compile more than 2 chapters together I get the following error: Server error, Sorry, something went wrong and your project could not be compiled. Please try again in a few moments. Trying again later does nothing to rectify the issue. This is in draft mode as well so images are not the issue.
EDIT: MWE included
documentclass[12pt, twoside]{report}
usepackage[utf8]{inputenc}
setlength{parindent}{0pt}
usepackage{parskip}
usepackage{setspace}
usepackage{array}
doublespacing
usepackage[a4paper, left=40mm, top=25mm, right=20mm, bottom=25mm]{geometry}
usepackage{graphicx}
graphicspath{{Images/}{../Images/}}
usepackage[outdir=./]{epstopdf}
usepackage{tabularx}
usepackage{multirow}
usepackage{arydshln}
renewcommand{arraystretch}{1.5}
usepackage{rotating}
usepackage{makecell}
usepackage[justification=justified]{caption}
usepackage{comment}
usepackage{fancyhdr}
pagestyle{fancy}
fancyhead{}
fancyhead[C]{Chapter thechapter}
setlength{headheight}{14.5pt}
fancyfoot{}
fancyfoot[RO,LE]{thepage}
usepackage[version=4]{mhchem} %for equations
usepackage{chemnum}
usepackage{xparse}
NewDocumentCommand{cecount}{ O{#2} m }{ce{#2} (cmpd{#1})}
usepackage{etoolbox,calc}
makeatletter
pretocmd{@makechapterhead}{setcounter{cmpdmain}{100*thechapter-1}}{}{}
makeatother
usepackage[journal = angew]{chemstyle}
cstsetup{radhyphen = false,radsuper = true,abbremph = true}
usepackage{chemscheme}
usepackage{siunitx}
usepackage[backend = biber, style=chem-angew]{biblatex}
addbibresource{mendeley.bib}
begin{document}
chapter{Introduction}
input{Chapters/chapter1.tex}
input{Chapters/chapter2.tex}
etc...
sharelatex compilation-error
I am trying to compile a large document with several chapters in ShareLatex. Each Chapter compiles correctly with minor (often unavoidable) errors but when I try to compile more than 2 chapters together I get the following error: Server error, Sorry, something went wrong and your project could not be compiled. Please try again in a few moments. Trying again later does nothing to rectify the issue. This is in draft mode as well so images are not the issue.
EDIT: MWE included
documentclass[12pt, twoside]{report}
usepackage[utf8]{inputenc}
setlength{parindent}{0pt}
usepackage{parskip}
usepackage{setspace}
usepackage{array}
doublespacing
usepackage[a4paper, left=40mm, top=25mm, right=20mm, bottom=25mm]{geometry}
usepackage{graphicx}
graphicspath{{Images/}{../Images/}}
usepackage[outdir=./]{epstopdf}
usepackage{tabularx}
usepackage{multirow}
usepackage{arydshln}
renewcommand{arraystretch}{1.5}
usepackage{rotating}
usepackage{makecell}
usepackage[justification=justified]{caption}
usepackage{comment}
usepackage{fancyhdr}
pagestyle{fancy}
fancyhead{}
fancyhead[C]{Chapter thechapter}
setlength{headheight}{14.5pt}
fancyfoot{}
fancyfoot[RO,LE]{thepage}
usepackage[version=4]{mhchem} %for equations
usepackage{chemnum}
usepackage{xparse}
NewDocumentCommand{cecount}{ O{#2} m }{ce{#2} (cmpd{#1})}
usepackage{etoolbox,calc}
makeatletter
pretocmd{@makechapterhead}{setcounter{cmpdmain}{100*thechapter-1}}{}{}
makeatother
usepackage[journal = angew]{chemstyle}
cstsetup{radhyphen = false,radsuper = true,abbremph = true}
usepackage{chemscheme}
usepackage{siunitx}
usepackage[backend = biber, style=chem-angew]{biblatex}
addbibresource{mendeley.bib}
begin{document}
chapter{Introduction}
input{Chapters/chapter1.tex}
input{Chapters/chapter2.tex}
etc...
sharelatex compilation-error
sharelatex compilation-error
edited Aug 30 '18 at 13:55
Tmr90
asked Aug 30 '18 at 13:34
Tmr90Tmr90
112
112
1
Everything will remain pure speculation unless you don't provide a Minimal Working Example.
– AlexG
Aug 30 '18 at 13:35
1
What happens when you compile locally?
– Jeffrey J Weimer
Aug 30 '18 at 13:37
1
I am trying to compile locally now to see if that works, thanks for the suggestion. MWE added above
– Tmr90
Aug 30 '18 at 13:55
1
It will compile locally but my references (biblatex) are now not working and the headers and footers and page numbers are messed up!
– Tmr90
Aug 30 '18 at 14:05
1
The commentcompiles correctly with minor (often unavoidable) errors
is very suspicious, no tex errors are unavoidable, and given tex's error recovery strategies I would never use any pdf generated by a tex run that makes any error. But you have not said what errors you get or given any other indication of the problem.
– David Carlisle
Aug 30 '18 at 16:50
|
show 4 more comments
1
Everything will remain pure speculation unless you don't provide a Minimal Working Example.
– AlexG
Aug 30 '18 at 13:35
1
What happens when you compile locally?
– Jeffrey J Weimer
Aug 30 '18 at 13:37
1
I am trying to compile locally now to see if that works, thanks for the suggestion. MWE added above
– Tmr90
Aug 30 '18 at 13:55
1
It will compile locally but my references (biblatex) are now not working and the headers and footers and page numbers are messed up!
– Tmr90
Aug 30 '18 at 14:05
1
The commentcompiles correctly with minor (often unavoidable) errors
is very suspicious, no tex errors are unavoidable, and given tex's error recovery strategies I would never use any pdf generated by a tex run that makes any error. But you have not said what errors you get or given any other indication of the problem.
– David Carlisle
Aug 30 '18 at 16:50
1
1
Everything will remain pure speculation unless you don't provide a Minimal Working Example.
– AlexG
Aug 30 '18 at 13:35
Everything will remain pure speculation unless you don't provide a Minimal Working Example.
– AlexG
Aug 30 '18 at 13:35
1
1
What happens when you compile locally?
– Jeffrey J Weimer
Aug 30 '18 at 13:37
What happens when you compile locally?
– Jeffrey J Weimer
Aug 30 '18 at 13:37
1
1
I am trying to compile locally now to see if that works, thanks for the suggestion. MWE added above
– Tmr90
Aug 30 '18 at 13:55
I am trying to compile locally now to see if that works, thanks for the suggestion. MWE added above
– Tmr90
Aug 30 '18 at 13:55
1
1
It will compile locally but my references (biblatex) are now not working and the headers and footers and page numbers are messed up!
– Tmr90
Aug 30 '18 at 14:05
It will compile locally but my references (biblatex) are now not working and the headers and footers and page numbers are messed up!
– Tmr90
Aug 30 '18 at 14:05
1
1
The comment
compiles correctly with minor (often unavoidable) errors
is very suspicious, no tex errors are unavoidable, and given tex's error recovery strategies I would never use any pdf generated by a tex run that makes any error. But you have not said what errors you get or given any other indication of the problem.– David Carlisle
Aug 30 '18 at 16:50
The comment
compiles correctly with minor (often unavoidable) errors
is very suspicious, no tex errors are unavoidable, and given tex's error recovery strategies I would never use any pdf generated by a tex run that makes any error. But you have not said what errors you get or given any other indication of the problem.– David Carlisle
Aug 30 '18 at 16:50
|
show 4 more comments
1 Answer
1
active
oldest
votes
You might need to willfully not understand how the site actually works and then post feature-request after feature-request about how to change it for the better. You'll surely net some pity upvotes! i.e server unavailable error show.
New contributor
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "85"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f448501%2fserver-error-compiling-big-documents-sharelatex%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
You might need to willfully not understand how the site actually works and then post feature-request after feature-request about how to change it for the better. You'll surely net some pity upvotes! i.e server unavailable error show.
New contributor
add a comment |
You might need to willfully not understand how the site actually works and then post feature-request after feature-request about how to change it for the better. You'll surely net some pity upvotes! i.e server unavailable error show.
New contributor
add a comment |
You might need to willfully not understand how the site actually works and then post feature-request after feature-request about how to change it for the better. You'll surely net some pity upvotes! i.e server unavailable error show.
New contributor
You might need to willfully not understand how the site actually works and then post feature-request after feature-request about how to change it for the better. You'll surely net some pity upvotes! i.e server unavailable error show.
New contributor
New contributor
answered 8 mins ago
cemlly rioscemlly rios
1
1
New contributor
New contributor
add a comment |
add a comment |
Thanks for contributing an answer to TeX - LaTeX Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f448501%2fserver-error-compiling-big-documents-sharelatex%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
Everything will remain pure speculation unless you don't provide a Minimal Working Example.
– AlexG
Aug 30 '18 at 13:35
1
What happens when you compile locally?
– Jeffrey J Weimer
Aug 30 '18 at 13:37
1
I am trying to compile locally now to see if that works, thanks for the suggestion. MWE added above
– Tmr90
Aug 30 '18 at 13:55
1
It will compile locally but my references (biblatex) are now not working and the headers and footers and page numbers are messed up!
– Tmr90
Aug 30 '18 at 14:05
1
The comment
compiles correctly with minor (often unavoidable) errors
is very suspicious, no tex errors are unavoidable, and given tex's error recovery strategies I would never use any pdf generated by a tex run that makes any error. But you have not said what errors you get or given any other indication of the problem.– David Carlisle
Aug 30 '18 at 16:50