Error 32000 with createds.exe; PLEASE HELP!
Hi all. I am getting an error when I am almost at the end of single-tier installation of the Beta 2 version. Upgraing to the latest release is not an option for me so could any one please help me through this?
The command line and the error are below:
C:\Program Files\Microsoft Visual Studio 2005 Enterprise Server\BISIISDIR\uninst
all>createds "http://FOUNDATIONSRVR/ReportServer/ReportService.asmx" TfsReportDS "Data source=FOUNDATIONSRVR;initial catalog=BisDWDB" "MARSFOUNDATION\TFSService" "01000000d08c9ddf0115d1118c7a00c04fc297eb01000000a07e8ac721d1d14c830e39f069f0b
ee000000000220000005500730065007200200049006e0066006f0072006d006100740069006f006
e00000003660000a800000010000000cabf44ca50bddfdc37cfa0fd1980d84c0000000004800000a
000000010000000cb6bca0c3c62b4c20d9280f7d631e9f6200000004f84ec8b02aab961aa25a1c4b
fdda8ad6519db6b8be0719855676f5f4a029e6d14000000c15c4660f30e2484febd86d0adef220de
59a42b5"
System.Net.WebException: The request was aborted: The connection was closed unexpectedly.
at System.Net.ConnectStream.InternalWrite(Boolean async, Byte[] buffer, Int32 offset, Int32 size, AsyncCallback callback, Object state)
at System.Net.ConnectStream.Write(Byte[] buffer, Int32 offset, Int32 size)
at System.Xml.XmlUtf8RawTextWriter.FlushBuffer()
at System.Xml.XmlUtf8RawTextWriter.Flush()
at System.Xml.XmlWellFormedWriter.Flush()
at System.Xml.Serialization.XmlSerializer.Serialize(XmlWriter xmlWriter, Object o, XmlSerializerNamespaces namespaces, String encodingStyle, String id)
at System.Xml.Serialization.XmlSerializer.Serialize(XmlWriter xmlWriter, Object o, XmlSerializerNamespaces namespaces, String encodingStyle)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Serialize(SoapClientMessage message)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at Microsoft.VisualStudio.ELead.ReportManager.RosettaProxy.ReportingService.C
reateDataSource(String DataSource, String Parent, Boolean Overwrite, DataSourceDefinition Definition, Property[] Properties)
at Microsoft.VisualStudio.ELead.Tools.createds.Program.Run(String[] args)
[2353 byte] By [
LeeKeel] at [2007-12-16]
I have exactly the same error with dual server setup.
When running the command from the command line, it comes back with:
System.Web.Services.Protocols.SoapException: The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing. (rsReportServerDatabaseUnavailable) > The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing. (rsReportServerDatabaseUnavailable) > Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at Microsoft.VisualStudio.ELead.ReportManager.RosettaProxy.ReportingService.CreateDataSource(String DataSource, String Parent, Boolean Overwrite, DataSourceDefinition Definition, Property[] Properties) at Microsoft.VisualStudio.ELead.Tools.createds.Program.Run(String[] args)
I tried setting the Directory security of Reports and ReportServer to anonymous, and iisreset for good measure. However, the problem still exists. I cannot seem to get around it.
Any help would be appreciated.
BTW I'm using Beta 2 en SQL Server 2005 April CTP. Report services are all (4) running, Report site can be reached from both machines with tfsservice.
Well, finally the single-server completed OK by following all steps of the installation guide. After that I noticed that the tfsservice account had become a member of the group IIS_WPG. So, I added that group to the tfsservice account in my dual-server environment, but alas, no success there. Still the createds.exe error.
Any actively refused connection is usually a firewall, blocking or not allowed issue. IIS (or whatever is listening/monitoring that port) basically is actively rejecting the connection.
Things to look for.
1. Firewalls or proxies are not allowing port access
2. The port is wrong and hitting one that is not allowed
The issue with login failure is because it is SQL does not allow Anonymous users to access it.
1. Please follow all instructions for installation
2. Ensure that the Team Foundation website does not allow anonymous access.
Overall, I would suggest the installation of Beta3. It has large improvements in regards to installation
--
Visual Studio Team System Beta3 is now available at MSDN Subscriber Downloads
--
This post is provided as is and does not always reflect the views of Microsoft Corporation. Any code samples contained are not supported.
