John Charles Olamendy
MSDN Magazine September 2009
View Complete Post
I have a queue whose activation I defined as below
ALTER QUEUE SomeInitiatorQueue
( STATUS = ON,
PROCEDURE_NAME = usp_SomeProc,
MAX_QUEUE_READERS = 30,
EXECUTE AS OWNER)
Now I am trying to access another database in usp_SomeProc as below
Select SomeColumn SomeOtherDb.dbo.SomeTable
Here I am getting this error "The server principal "sa" is not able to access the database "SomeOtherDb" under the current security context."
It never allows unless I grant all permissions on the database to all.
what is the solution?
I recently completed an in-place upgrade from WSS 3.0 to SharePoint Foundation 2010 to SharePoint Server 2010. While the first half of this migration process seems to have worked from WSS 3.0 to Foundation 2010 the upgrade from Foundation 2010 to Server
2010 has left the installation with only the Foundation level service applications.
If I go to add a new service application the only ones listed are the foundation service applications but if I go to check the current license it confirms the enterprise server edition is installed. I have re-ran the product configuration wizard and if I
check the patch status in central administration it confirms that all the enterprise components are installed they just aren't showing up in the service applications listing!
Any ideas on how I can add these missing services to central administration?
Use the Team Foundation Server EventService to create and manage event subscriptions or create a Web service to receive and process events.
Brian A. Randell
MSDN Magazine May 2008
MSDN Magazine March 2007
Who would have believed that XML, such a seemingly trivial technology, could revolutionize an industry? It may have seemed like a long shot in the beginning, but the XML aficionados saw something special and pragmatic right away-a sort of duct tape for the world's information systems.
MSDN Magazine November 2005
Throughout this issue, you'll read all about the promise of Web Services and how the .NET Framework enables Web Service development. Many people will also be building their Web Services atop C++ code and frameworks like ATL Server, particularly when performance is paramount. In this article, the authors show how fully functional Web Services are built using ATL Server and Visual Studio .NET. Beginning with unmanaged C++ classes, they add ATL attributes that make the code work over HTTP.
Kirk Fertitta and Chris Sells
MSDN Magazine December 2002
Web Services are all about exchanging data in the form of XML messages. If you were about to design a database schema, you probably wouldn't let your tool do it for you. You'd hand-tool it yourself to ensure maximum efficiency. In this article, the author maintains that designing a Web Service should be no different. You should know what kind of data will be returned by Web Service requests and use the structure of that data to design the most efficient message format. Here you'll learn how to make that determination and how to build your Web Service around the message structure.
When developing high-performance applications for the Web, developers often must choose between performance and ease of development. With ATL Server, new with Visual Studio .NET, developers get the best of both worlds. ATL Server uses a tag replacement engine written in C++, provides a simple programming model, and promotes enhanced performance and easy debugging. This article presents an overview of the ATL Server architecture, then creates a basic ATL Server project. It then goes on to explain processing SRF files, HTTP streams, forms, cookies, and header files. Managing session state is also discussed, along with file uploads and performance monitoring.
Shaun McAravey and Ben Hickman
MSDN Magazine October 2000
I have a serious problem that cannot be solved by googling around the keywords below: sharepoint, moss 2007, reporting service, ssrs 2008, rendering, internal server error, ....
The error is;
"An error occurred during client rendering. The remote server returned an error: (500) Internal Server Error. "
Everything is O.K.;
* When I render the report from the REPORTSERVER (http://localhost/ReportServer) * When the reports are scheduled to be sent by the reporting service (planned via MOSS 2007)ÃÂ
But if I open (render) the RDL file from the sharepoint REPORTS LIBRARY interface, all of the reports fail with that internal error message above.ÃÂ
It is weird also that parametrized reports are displayed without errors although the parameters are queried from a sql dataset. But I got the error when rendering the report after I've chosen a parameterÃÂ and order "apply/report"...
Possible causes how I met that error may be;
After I have installed (then uninstalled) AJAX extensions After I have re-configured IIS Web Service Extensions list items
Possible solution alternatives I've found;
I've found a solution on MSDN replying a similar issue with an ideal cause of the error but an evreka answer but no sol