Multiplicity Pro 1.26

Having trouble connecting MP secondaries

I have created a support ticket with Stardock with the only response of we are going to close your case because I have not replied within X amount of time.  I need help on this ASAP as was mentioned in the ticket.  Ticket #WEA-574670

The problem we are having is when trying to connect to secondary machines the user name and password seem to get corrupt.  After this MP tries to connect but 2 seconds later drops the connection.  Sometimes I can remove the secondary from the list and then add it again and it will be fine.  I have 7 machines to add but have been unable to get more than two to stay connected.

Any help would be great,

Matt

2,608 views 7 replies
Reply #1 Top

Hello.

I've received you ticket and responded.  

It appears that you responded more than once, and that bumped your ticket to the end of the queue

Reply #2 Top

Well the only response that I have been getting is that if I didn't reply to the email that the case was going to be closed.  Below is the emails that I've been getting.  So am I not supposed to reply to this email even though it implies to?  Note:  this is the first email I have recieved after opening this case followed be five of the same emails.  I have still not recieved any support on this matter.

 

[email protected],
This message is regarding your Ticket ID #WEA-574670. We are changing the status of this ticket to 'Closed' as we have not received a response from you in 48 hours. Should you wish to reopen the case, simply reply to this message and the ticket will be reopened.

   Subject: A customer has a question/request regarding Stardock's products
   Department: Multiplicity
   Priority: Support
   Status: On Hold

Please let us know if you have any additional questions.

Stardock Corporation

Reply #3 Top

Hmmm....

 

 

Reply #4 Top

There was an issue with our esupport system that was causing those emails to be sent at the wrong times, so I do apologize for that.  If ever get one of those emails, it may be an indication that either your or our response may not have been received for one reason or another.  You can always go directly through https://esupport.stardock.com/ using the email address you used to open the ticket, and the password that was included with your initial auto-response.

Reply #5 Top

Thanks Rosco for your reply.   Now I am wondering what is going to be the soonest I may get some support?????   I think I am due some since this ticket was origianally opened on Oct. 27th....

Reply #7 Top

Not sure what the problem is but I have sent Aaron Klenke some logs per his request along with some screen shots on Nov 16 and have not recieved any response back.  Is this issue being followed up on???