Need help when set up litwarehr

Topics: Datamodel, Setup
Dec 22, 2008 at 2:34 AM
Hello everyone,
         I want to try litwarehr in my vmware(MS server 2008+SQL Server 2005SP2+ VS2008SP1).
         I download the May2008 release. install the MSI file.Run the shotcut in created on my desktop and have all the prerequisites checked. 
        When the wizard run to the Sitka Configaration window,which ask me to input a Sitka Credentials(username and password) and the AuthorityId(the name you want for the Sitka authority). I input my username and password which I got from https://accesscontrol.ex.azure.microsoft.com/ManageAccount.aspx (I could change my password here:)). 
        And the AuthorityId I just input "Litwarehr" since I do not know what should I input. You see, I just want to run litwarehr without any change, so does anybody tell me what to input?
       Anyhow when I input "Litwarehr"as the AuthorityId and click the "OK" button, I got a error as following:
            An error has occured:
            System.ServiceModel.EndpointNotFoundExcepption: There was no endpoint listening at http://data.sitka.microsoft.com/soap/v1 that could accept the message. This is offen caused by an incorrect address or SOAP action. See innerException, if present, for more details.--->System.Net.EWbException:The remote name could not be resolved:'data.sitka.microsoft.com' at System.Net.HttpWebRequest.GetRequestStream() at System.ServiceModel.Channels.HttpOutput.WEbRequestHttpOutput.GetOutputStream()


     I have tried to find out some infomation in through the websites, maybe the endpoint is a wrong addressSome body told me that The endpoint to SDS should be https://database.windows.net/soap/v1/.  (http://social.msdn.microsoft.com/Forums/en-US/getstartnetandsqlservices/thread/87e118d5-bb72-4703-b21c-64dd5b9c7f0d/) But how can I chage the endpoint? May I just change all the endpoint address http://data.sitka.microsoft.com/soap/v1 to https://database.windows.net/soap/v1 ? It seems that does not work?


      I really need some one who have run the litwareHr(May 2008 Release)to give some help.

     Thanks in advance. 
Coordinator
Jan 21, 2009 at 3:51 PM
Hi there!

I'm back again. The thing is that there were a lot of changes on the underlying technologies that LitwareHR relies on since it was released. SDS (SQL Data Services is one such technology). The problem is that SDS endpoints have changed.

We can't ship Litware with pre-configured settings becuase SDS is a public service and everyone would be using the same instance. So the little utility simply allows you to define your authority, your user and your password and will:
 
- Provision configuration data needed by LW in the newly SDS authority
- Configure app.configs in the solution with the new values

So, the first thing you need to do is to change the app confg in this utility project to point to the updated SDS endpoints (The project is LitwareHR.Portfolio.Deployment). Re-run it again (supplying your own SDS credentials) and update the rest of the app.configs.

I have just installed a brand new Win2008 server in my lab. I will go through these steps and will post the findings here. Hopefully this will solve these issues.

Cheers
Eugenio

Jan 22, 2009 at 9:05 AM
Hi!

I'm with exactly same problem as Richard. The endpoints are wrong. So, I changed it to https://database.windows.net/soap/v1/ and I got a different exception.
This URL works very well under the browser. Just pay attention that url uses HTTPS instead HTTP that was used on old version of SDS.

---------------------------
An error has occurred
---------------------------
System.ArgumentException: The provided URI scheme 'https' is invalid; expected 'http'.
Parameter name: via
   at System.ServiceModel.Channels.TransportChannelFactory`1.ValidateScheme(Uri via)
   at System.ServiceModel.Channels.HttpChannelFactory.ValidateCreateChannelParameters(EndpointAddress remoteAddress, Uri via)
   at System.ServiceModel.Channels.HttpChannelFactory.OnCreateChannel(EndpointAddress remoteAddress, Uri via)
   at System.ServiceModel.Channels.ChannelFactoryBase`1.InternalCreateChannel(EndpointAddress address, Uri via)
   at System.ServiceModel.Channels.ChannelFactoryBase`1.CreateChannel(EndpointAddress address, Uri via)
   at System.ServiceModel.Channels.ServiceChannelFactory.ServiceChannelFactoryOverRequest.CreateInnerChannelBinder(EndpointAddress to, Uri via)
   at System.ServiceModel.Channels.ServiceChannelFactory.CreateServiceChannel(EndpointAddress address, Uri via)
   at System.ServiceModel.Channels.ServiceChannelFactory.CreateChannel(Type channelType, EndpointAddress address, Uri via)
   at System.ServiceModel.ChannelFactory`1.CreateChannel(EndpointAddress address, Uri via)
   at System.ServiceModel.ChannelFactory`1.CreateChannel()
   at System.ServiceModel.ClientBase`1.CreateChannel()
   at System.ServiceModel.ClientBase`1.CreateChannelInternal()
   at System.ServiceModel.ClientBase`1.get_Channel()
   at Shp.Runtime.Sitka.ServiceGateway.SitkaClient.SitkaSoapServiceClient.Create(Scope scope, Entity entity) in c:\LitwareHR\solution\LitwareHR\Shp.Runtime.Sitka.ServiceGateway\Service References\SitkaClient\Reference.cs:line 370
   at LitwareHR.Portfolio.Deployment.DeploymentServices.CreateAuthority(String userName, String password, String authorityId) in c:\LitwareHR\solution\LitwareHR\LitwareHR.Portfolio.Deployment\DeploymentServices.cs:line 125
   at LitwareHR.Portfolio.Deployment.MainForm.okButton_Click(Object sender, EventArgs e) in c:\LitwareHR\solution\LitwareHR\LitwareHR.Portfolio.Deployment\MainForm.cs:line 54
---------------------------
OK   
---------------------------

Seems that is something wrong on the endpoint configurations.
I have other questions too... The config utility asks for:

Username and password: It is my passport .net associated to my Azure services account?
Authorit ID: What should I put here? My project name under Azure services?

Waiting for one solution...

Thanks for support...

Gutemberg Ribeiro
Coordinator
Jan 22, 2009 at 4:31 PM
Edited Jan 22, 2009 at 4:32 PM
see this thread

http://www.codeplex.com/LitwareHR/Thread/View.aspx?ThreadId=44796


In essence, besides the address you need to change the security mode to "Transport"
Jan 22, 2009 at 6:48 PM
Ok I changed the transport level but now I get other error, seems related to my credentials... I already have one Azure account working but, what credentials should I provide? My .net passport?


On 22/01/09 15:31, "eugeniop" <notifications@codeplex.com> wrote:



From: eugeniop

see this thread

http://www.codeplex.com/LitwareHR/Thread/View.aspx?ThreadId=44796



Read the full discussion online <http://www.codeplex.com/LitwareHR/Thread/View.aspx?ThreadId=42804&ANCHOR#Post149816> .


To add a post to this discussion, reply to this email (LitwareHR@discussions.codeplex.com <mailto:LitwareHR@discussions.codeplex.com?subject=[LitwareHR:42804]> )


To start a new discussion for this project, email LitwareHR@discussions.codeplex.com


You are receiving this email because you subscribed to this discussion on CodePlex. You can unsubscribe <http://www.codeplex.com/site/discussions/thread/unsubscribe/42804> on codePlex.com.


Please note: Images and attachments will be removed from emails. Any posts to this discussion will also be available online at codeplex.com


Coordinator
Jan 23, 2009 at 3:05 AM
No passport (LiveID) is required. Just your SQL Data Services credentials (solution name + password). Could you post your exception?
Jan 23, 2009 at 2:36 PM
---------------------------
An error has occurred
---------------------------
System.ServiceModel.Security.MessageSecurityException: The HTTP request was forbidden with client authentication scheme 'Basic'. ---> System.Net.WebException: The remote server returned an error: (403) Forbidden.
   at System.Net.HttpWebRequest.GetResponse()
   at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
   --- End of inner exception stack trace ---

Server stack trace:
   at System.ServiceModel.Channels.HttpChannelUtilities.ValidateAuthentication(HttpWebRequest request, HttpWebResponse response, WebException responseException, HttpChannelFactory factory)
   at System.ServiceModel.Channels.HttpChannelUtilities.ValidateRequestReplyResponse(HttpWebRequest request, HttpWebResponse response, HttpChannelFactory factory, WebException responseException)
   at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
   at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
   at System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message message, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs)
   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at Shp.Runtime.Sitka.ServiceGateway.SitkaClient.ISitkaSoapService.Create(Scope scope, Entity entity)
   at Shp.Runtime.Sitka.ServiceGateway.SitkaClient.SitkaSoapServiceClient.Create(Scope scope, Entity entity) in c:\LitwareHR\solution\LitwareHR\Shp.Runtime.Sitka.ServiceGateway\Service References\SitkaClient\Reference.cs:line 370
   at LitwareHR.Portfolio.Deployment.DeploymentServices.CreateAuthority(String userName, String password, String authorityId) in c:\LitwareHR\solution\LitwareHR\LitwareHR.Portfolio.Deployment\DeploymentServices.cs:line 125
   at LitwareHR.Portfolio.Deployment.MainForm.okButton_Click(Object sender, EventArgs e) in c:\LitwareHR\solution\LitwareHR\LitwareHR.Portfolio.Deployment\MainForm.cs:line 54
---------------------------
OK   
---------------------------
Coordinator
Jan 24, 2009 at 6:22 PM
You are not using the right credentials with SDS.

Open a browser, type https://<your authority>.data.database.windows.net/v1/LitwareHR?q=

You will be prompted for username + password. If it works, then make sure the web.config files indicated in the other thread are configured correctly.