LaTeX.org

This issue has already been reported on the bugtracker

Does the PDF build when you build it without opening a viewer (F7)?
If it does not, then look in the buildwindow for errors and warnings. This will help you identify the source of your problem.

The best answer concerning all AdobeReader related errors is just not to use it.
It is buggy and bloated ...

Nothing you wrote makes any sense.
"No pdf output produced" is not from texniccenter but from pdftex, and has absolutely NOTHING to do with texniccenter, restarting Texniccenter could not have had any effect on it whatsoever.
What I can imagine is that the texfiles were locked by another application ...

I don't believe that this is the dev's priority right now.
It'll probably be implemented when version 2 is nearing its beta stage.

Problem is probably related to a bad install.
Uninstall miktex and reinstall it again.
I have no problems whatsoever with miktex/texniccenter (1/2alpha) on a x64 system.

Another solution could be that Miktex 2.8 offers two different settings, for user and for admin. Use the admin settings to allow ...

Or use pdf xchange. It always remembers the last position and opens the file at the exact same spot

Cannot confirm, Build 1064 runs fine on Win7 x64 and WinXP-SP3

The "Writing Subversion Build Number"-Error is because your apparently did not use the TortoiseSVN's "SVN Update" function to get the source

For the other errors:
It appears that you have used the debug and/or the release profile: but you have to choose either the UNICODE debug or the UNICODE ...

Is it possible in the alpha to rerun the structure-parser again without restarting the whole application?
The reason I'm asking is that I would like to refresh the references after adding another article to the .bib file externally.

And a new Issue: MSXML related
it was introduced with the x64 fixes in build 1059
Build Config: Unicode Release (win32)

When i try to export or import output profiles, I get the following error:
"It is an error to mix objects from different versions of msxml"
Progid: msxml6.dll
Works fine with ...