Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
Few minutes ago 3 DB on one SQLAzure sever disappeared and the management console tell me that there are problems to retrieve information about the databases on specific SQL Server of West Europe region.
In the "Support" section we are not able to send a tecnical question, only billing question.
But this is NOT a QUESTION, this is a SIGNAL !!!! (Microsoft is becoming a wall of gum?)
Any one have any way to inform MS that theirs 99.95% up-time services are off???
Many thanks in advance.
Have nice week-end.
Davide.
If you don't see a "Technical" option in the drop down on the support form you'll likely see below the form something that says "Your Support Plan: Free - billing support only
Your current plan does not include technical support from Microsoft.". This means that you haven't purchased support, which comes with the web incident submittal. It will also have a link to the following page https://www.windowsazure.com/en-us/support/plans/, which describes the support levels.
Sadly, at the free support level there doesn't even seem to be a way to tell them that something seems wrong other than to post to the forums. If you are a MSDN Subscriber there is a link on that same support forum that leads you off to a different form which I believe will start an online chat.
In addition the service dashboard gets updated when issues are discovered and they have information to post. Just because something isn't showing up yet doesn't mean that they aren't aware of an issue.
Related
Closed. This question is not reproducible or was caused by typos. It is not currently accepting answers.
This question was caused by a typo or a problem that can no longer be reproduced. While similar questions may be on-topic here, this one was resolved in a way less likely to help future readers.
Closed yesterday.
Improve this question
Three years ago I developed an integration with Amazon, returning sales data of goods sold via FBA, and, for the whole time, it had been working literally flawlessly. Since Friday, 13 March, I have been facing a problem with Amazon MWS API: it still generates the FBA sales report, but stopped returning personal information, like buyers'/recipients' full names and their addresses. All the other data is present in the report. And absolutely nothing was done with the integration itself, neither with its configuration.
I can only add that I am internal developer of the organization (not a 3rd party producing solutions for other companies) and I have full access to the seller central console, so this is not an access issue. Our developer account under APPS & SERVICES -> DEVELOP APPS remains active.
Any ideas...?
Amazon restricted PII (Personal Identified-able Info). You need to talk to them to regain your access.
Thanks.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I'm launching a startup web site, what i would like to know is how to start with that, i mean is better to use invitations first of all?
Then how to send invitations and to who?
How can i plan invitations? Which are best practices?
Does anyone is passed from this step with his own site?
Any experience on here?
thanks
Whether you create a beta version of the site first is completely up to you.
It really depends what type of website you're planning to make. Beta's are obviously a good way to gain feedback on your website and its functionality before releasing to everyone. Thus, allowing you to make improvements/fix bugs before everyone uses the site.
In terms of actually getting users for the beta, it's very much a case of marketing your website and its existence well (through social media, advertising etc.), and then providing some kind of 'sign up for the beta' page. You could then close registration for the beta once you have enough users, and devise some method of gaining feedback from users.
I haven't personally created a beta myself, but if I was to do it, I would do the above.
Hope that's of some help.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
We are using this server for almost a year now.
Last forum post seen in November, 2011.
Last server version released 28/03/12.
Just wondering if anyone knows whats happening inside the company?
Should we expect something or should we start looking for alternatives?
I did what you did not do: using email to ask the question to the people able to answer.
And they replied that:
the forum was closed because they could not cope with the amount of accounts created daily to publish junk
the next version will be the most important ever made for G-Wan, with new features like a caching reverse proxy and an elastic load-balancer as well as system replacements like a wait-free memory allocator.
With regard to such developments, a 3-month period without publishing releases sounds reasonable.
More reasonable than assuming that such an 'inactivity period' means that "the project is dead".
Would you say that for other Web servers like Apache which have much larger release cycles?
You should always be expecting something from G-WAN. It's a great piece of software. Here's the other thing too: G-WAN was expertly engineered. That doesn't mean that there are no bugs in it, or that features can't be implemented, but G-WAN is incredibly tight.
It has lean code, it does what it supposed to do, very well, and it is built for the developer to add in the functionality that hasn't been put in there yet.
That's the beauty of it, or one facet of the beauty.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
I want to create a SharePoint Server setup that will allow applications to be highly avaliable. Say if we have a portal in SharePoint, and I wanted to make it available always. I know it has to do with WFE. Someone guide me with article or Arch that need to be set for this.
Having multiple WFE (Web Front-ends) will make the web part of your SharePoint more reliable -- if one goes down, you can have your load-balancer stop sending requests to it. There is no way to ensure 100% uptime -- reliability is a combination of having redundancy (in hardware and services), monitoring, 24x7 staff to fix problems, etc.
Some things to look at:
Plan for Redundancy
http://technet.microsoft.com/en-us/library/cc263044.aspx
Plan for Availability
http://technet.microsoft.com/en-us/library/cc748832.aspx
There are third-party products that can help with fail-over, but I haven't used one to recommend.
See Lou's links. You can have redundant WFEs, query servers, and application servers as well as cluster your database.
Note that you cannot have a redundant index server unless you have two SSPs that basically index the same content. The query servers get the index replicated on them, so if the index server goes down you can still perform a query, the index will just not be updated until the index server comes back online. If you can't get it back online you will need to rebuild your index (full crawls).
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 9 years ago.
Improve this question
I am investigating the feasibility of setting up a discussion forum / message board in my company to enable knowledge sharing etc.
What are the steps involved in implementing such a solution?
I would definitely recommend a Wiki - we've used Mindtouch internally for a number of years and have also posted all of our documentation externally on a wiki.
The steps will depend on what technology you already have in place and what kind of shop you are. If you have SharePoint (WSS 3.0 or MOSS 2007), then you already have blog, wiki and discussion group functionality built in. Not the best in the world, but it's there.
A shop that uses more open source tools is less likely to find SharePoint compelling. ;-)
Instead of (or maybe in addition to) a discussion forum, I would recommend a wiki server. This way you can have different howtos, lists, documentation, etc available and the important things will tend to stay up to date. We have one in our department and it is quite useful (if only people would log in when editing...).
I was not involved in setting it up, so I cannot give any details on that, but it is based on mediawiki.