How can we help you today? How can we help you today?
Xaphan
I realized that this ticket was closed before I posted my last response. I have re-posted the response as a new issue to... http://www.red-gate.com/MessageBoard/viewtopic.php?p=61215#61215 / comments
I realized that this ticket was closed before I posted my last response. I have re-posted the response as a new issue to...http://www.red-gate.com/MessageBoard/viewtopic.php?p=61215#61215
0 votes
Thanks for the reply. I looked in to this issue further and here is what I found... I was able to get SQL Compare to work with the following command line on my personal workstation: "C:\Program Files (x86)\Red Gate\SQL Compare 10\sqlcompare.exe" /sourcecontrol1 /revision1:HEAD /s2:MyDatabaseServer /db2:MyDatabaseName /o:Default /Include:identical /sfx:Automated.xml /sync Automated.xml was located in the directory that I ran the command line from. I tried this again on my build server using the exact same command and got the following error: Error: The file 'Automated.xml' containing the script folder location XML fragment could not be parsed. Check that the file exists and that its contents are well-formed. My build server has both SQL Compare and SQL Source Control installed and they are both the same version as on my workstation. They also are located in the same directory. The Automated.xml is also located in the directory where I am calling the the command line from on the build server. Why is my workstation running the command prompt without errors, but the exact same command is giving me error on my build machine? Does my build machine need something installed or setup in order to make it work? / comments
Thanks for the reply. I looked in to this issue further and here is what I found... I was able to get SQL Compare to work with the following command line on my personal workstation:"C:\Program Fil...
0 votes