Dr. Thomas Oden, A theologian who made made no new contribution to theology

Who is Thomas Clark Oden?


Thomas Clark Oden was an American United Methodist theologian and religious author. He is often regarded as the father of the paleo-orthodox theological movement and is considered to be one of the most influential theologians of the 20th century and the beginning of the 21st century.

Quotes & Works

  1. “The heart of my story is that the first part of 40 years of my life, I was way, way out there on a path that I had to go on in order to come back like the prodigal son to the father,” Oden told Al Mohler, president of Southern Baptist Theological Seminary, in a 2015 interview. “But eventually I did and by my 40th year, I became deeply invested in listening carefully to the classical Christian consensus … of the ancient Christian writers and their interpretation of Scripture.”
  2. On Passing
    • Mark Tooley, Institute on Religion & Democracy president
      • “Tom is now with the early saints whose lives and teachings he studied so closely,” said Institute on Religion & Democracy president Mark Tooley, who called him “a dear friend and counselor, a brilliant and cheerful warrior for good causes, irreplaceable.
    • Russell Moore, president of the Ethics and Religious Liberty Commission
      • “What a loss to us all is the death of [Oden]. He is a hero of orthodox conviction,” tweeted Russell Moore, president of the Ethics and Religious Liberty Commission.
  3. Paleo-orthodox
    • Fred Sanders
      • Fred Sanders, theology professor at Biola University, remembered Oden as a “paleo-orthodox champion of the classic, consensual Christian tradition.”
    • Michael Patton, Credo House

      • Oden coined the term paleo-orthodox, explained here ,  here by Credo House’s C. Michael Patton as:

        • This is the belief that the Christian faith can be found in the consensual beliefs of the church. This is a form of “consensual orthodoxy” (consensus fidelium). This search for consensus follows the dictum of Saint Vincent of L’rins: quod ubique, quod semper, quod ab omnibus, “that which was believed everywhere, always.” Normally, according to Thomas Oden, who coined the term “paleo-orthodoxy,” this consensual faith can be found in the first five centuries of the Christian church (Oden, Requiem: A Lament in Three Movements), before the “speculative scholasticism” of western Catholicism. The idea of theological progression is normally thought by strict adherents of Paleo-Orthodoxy as a post-enlightenment influenced methodology that should not be followed.

  4. Prolific
    • Oden wrote and edited hundreds of books, articles, and essays and gave speeches on such topics as church and the world, church controversies, evangelicalism, Kierkegaard, the Methodist church, church discipline, John Wesley, postmodernism, and others. His first volume with InterVarsity Press was Two Worlds (1992), which discussed the dichotomy of perishing modernity and emerging post modernity, and their impact on Christianity. He quickly followed this with the launch of the [ACCS] in 1998, forever changing the face of IVP’s publishing program.
  5. Association of Classical and Christian Schools

    • J. I. Packer

      • The ACCS’s patristics exposition was praised by Packer as “badly needed for several centuries, and the whole Christian world should unite to thank those who are undertaking to fill the gap.”
    • Joel Scandrett, director of the Robert E. Webber Center at the Trinity School for Ministry

      • One of Oden’s many former students, Joel Scandrett, director of the Robert E. Webber Center at the Trinity School for Ministry, said the theologian “passed on to me and generations of students his great love of the Triune God and the ancient legacy of patristic exegetical and trinitarian theology.

      • “His lifetime of work,” said Scandrett, “reveals that Christians need to rely upon the wisdom of the historical church, particularly the early church, rather than exclusively on modern scholarship and theology.”

  6. He made no new contribution to theology
    • Oden told CT in 1990 that he dreamed his epitaph would read: He made no new contribution to theology. He said:
      • In my dream I was extremely pleased, for I realized I was learning what Irenaeus meant when he warned us not to invent new doctrine. This was a great discovery for me. All my education up to this point had taught me that I must be compulsively creative. If I was to be a good theologian I had to go out and do something nobody else ever had done. The dream somehow said to me that this is not my responsibility, that my calling as a theologian could be fulfilled through obedience to apostolic tradition.


  1. Dr. Thomas Oden, author of How Africa Shaped the Christian Mind
    • Profile
      • Dr. Tom Oden, author of How Africa Shaped the Christian Mind, speaks with Dr. Jerry Pattengale of The Green Scholars Initiative about the role of Africa in the early Church
    • Videos
      • Video #1
        Channel :- InterVarsity Press
        Published On :- 2014-Jan-6th
  2. Libyan Christianity 1: A Libyan History Awaiting Discovery – Thomas C. Oden
    • Profile
      • Thomas Oden, professor of Theology Emeritus, Drew University; General Editor, Ancient Christian Commentary on Scripture, explores historical Christianity by means of understanding the ancient culture and historical underpinnings of the people of Libya.
    • Videos
      • Video #1
        Channel :- Dallas Theological Seminary
        Published On :- 2012-July-27th

In depth

Dr. Thomas Oden, author of How Africa Shaped the Christian Mind

  1. 215 to 230 AD
  2. Christians in Palestine
  3. Intellectual Energy from South to North

Libyan Christianity 1: A Libyan History Awaiting Discovery – Thomas C. Oden

  1. Struggle of Rural Christianity
    • Conflict
      • North South Conflict
      • East west conflict
      • Christian/Islam Conflict
    • Undercurrent
      • Visa
      • Lockerbie
  2. Archbishop
  3. Socialism


  1. Wikipedia
    • Thomas C. Oden


Reporting Services – Errors – ‘The feature: “Scale-out deployment” is not supported in this edition of Reporting Services. (rsOperationNotSupported)’


Post upgrade of Microsoft’s SQL Server, trying to access Reporting Services, ran into an error.


Error Image


Error Textual

The feature “Scale-out deployment” is not supported in this edition of Reporting Services.  (rsOperationNotSupported).

Trouble Shooting


  1. Confirm SQL Server Edition
  2. Review registered encryption keys for the Report Server Instance

Confirm SQL Server Edition

Launch SQL Server Query tool and issue a query that will help determine SQL Server Edition:


select @@version as [version]


Output Image


Output Textual

Microsoft SQL Server 2017 (RTM-CU12) (KB4464082) - 14.0.3045.24 (X64)
Oct 18 2018 23:11:05
Copyright (C) 2017 Microsoft Corporation
Standard Edition (64-bit) on Windows Server 2012 R2 Standard 6.3  (Build 9600: ) (Hypervisor)


  1. We are running SQL Server
    • Marketing :- v2017
    • RTM/Service Pack :- RTM
    • Cumulative Patch :- CU12
    • Edition :- Standard Edition

Review registered encryption keys for the Report Server Instance

using same query tool you used to determine SQL Server’s Version Number, please review the contents of the ReportServer.dbo.keys table.


select *

from [ReportServer].dbo.[Keys]


Output Image

ReportServer.dbo.keys.01.20181111.0342PM [brushedup].png


  1. We have three entries
    • Records
      • Installation ID
        • 00000000-0000-0000-0000-000000000000
          • We can skip for now
        • BDEBD908-9B5E-4971-B6A5-0E6EB267A2CA
          • InstanceName = SSRS
            • SSRS is the new instance name for SQL Server Reporting Services
            • And, we can confirm that it is the one post upgrade
          • InstanceName= MSSQLSERVER
            • MSSQLSERVER is pre-upgrade name
            • We can remove it



  1. Backup database table
  2. Remove previous key

Backup database table

Let us backup ReportServer.dbo.keys


if schema_id('dbBackup') is null

create schema [dbBackup] authorization [dboo];


select *

into   [ReportServer].[dbBackup].[keys.20181115.0607AM]

from   [ReportServer].[dbo].[keys]

Remove Previous Key

Remove previous key from ReportServer.dbo.keys


from   [ReportServer].[dbo].[keys]
where  InstanceName = 'MSSQLSERVER'

BitLocker – Configuration – Error – “Unable to find the Reporting Services instance name”


Recently we ran into an “ha ha” moment installing Microsoft BitLocker.


BitLocker Administration and Monitoring

Configuring Reports

Here is the “Configuring Reports” window.



Error Image


Error Text

Unable to find the Reporting Services instance name <server-name>\MSSQLServer

Trouble Shooting

Reporting Services Configuration Tool ( RSConfigTool )

Launched SQL Server Reporting Services Configuration Tool ( RSConfigTool).


Ensured that the service is running and noted the Instance ID.

The Instance ID is SSRS.


BitLocker Administration and Monitoring

Configuring Reports

For the instance name, please note the instance name recorded earlier.

That instance name is SSRS.

Configuration SSRSDB.20180720_1041AM



Sapien – WMI Explorer – Reporting Services Configuration Manager


Wanted to utilize another WMI Query tool in addition to Microsoft’s own WMI tools.




SQL Server Reporting Services (SSRS) – Error – “Invalid Class”

In the “SQL Server Reporting Services (SSRS) – Error – Invalid Class” post, we bemoaned the difficulty of fully espousing our wilderness experience based on screenshots from a single tool; that tool being Microsoft WMI Explorer.

The post is here.

Microsoft’s WMI Explorer is available at Codeplex and here is the specific URL.



We wanted to try out one more tool and the one we chose is Sapien WMI Explorer.


Please download WMI Explorer from here.

The current version is 2.2.74.


  1. OS Version
    • Desktop :- Windows 7 / Windows 8 / Windows 8.1 / Windows 10
    • Server :- Windows Server 2008 R2 / Windows Server 2012 / Windows Server 2012 R2
  2. OS Bitness
    • 32 and 64 bit
  3. Powershell
    • Version :- Powershell Version 3.0
  4. Visual Studio 2012 Runtime



Installation is straightforward.


Connect to the Vendor’s web site and request a trial key.



Launch Sapien’s WMI Explorer and navigate the Class Browser tree.

As one chooses a specific Namespace, the classes and corresponding properties and methods for that class are shown in the right window.

We are interested in SQL Server Namespace and specifically the ReportServer space.

Please click on the Query button on the Ribbon Tab to view and edit queries.


Pasted below are the images captured from our journey.


Hierarchy – \\<Host>\ROOT\Microsoft\SqlServer

Hierarchy – \\<Host>\ROOT\Microsoft\SqlServer\ReportServer

Hierarchy – \\<Host>\ROOT\Microsoft\SqlServer\ReportServer\<Instance>
Instance – Default

Instance – DATACAP


Hierarchy – \\<Host>\ROOT\Microsoft\SqlServer\ReportServer\<Instance>\<Version>
Instance – {RS_DATACAP }\ Version {v12}

Instance – {RS_DATACAP }\ Version {v12} – Custom Query

Instance – {RS_DATACAP }\ Version {v12} – Query Results

Hierarchy – \\<Host>\ROOT\Microsoft\SqlServer\ReportServer\<Instance>\<Version>\Admin
Instance – {RS_DATACAP }\ Version {v12} \ Admin – Custom Query

Instance – {RS_DATACAP }\ Version {v12} \ Admin – Query Results


WMI – Reporting Services Configuration Manager – Event Viewer


When troubleshooting Reporting Services Configuration Manager WMI calls it can be useful to see whether WMI activities are occurring.



Event Viewer

Enable Log

WMI calls are logable in the Event Viewer.

But, they are not logged by default.

To enable logging please follow the steps listed below:

Obtaining WMI Events Through Event Viewer

  1. Open Event Viewer. On the View menu, click Show Analytic and Debug Logs
  2. Locate the Trace channel log for WMI under Applications and Service Logs | Microsoft | Windows | WMI Activity
  3. Right-click the Trace log and select Log Properties. Click the Enable Logging check box to start the WMI event tracing
  4. WMI events appear in the event window for WMI-Activity. Double-click an event in the list to see the detailed information. You can view an event in XML View or in Friendly View format.

Logged Events


# Event
1 GroupOperationId = 159602; OperationId = 159602; Operation = IWbemServices::Connect; ClientMachine = QADB; User = dadeniji.adeniji; ClientProcessId = 5024; NamespaceName = \\QA\root\Microsoft\SqlServer\ReportServer
2 GroupOperationId = 159603; OperationId = 159604; Operation = Start IWbemServices::CreateInstanceEnum – __NAMESPACE; ClientMachine = QADB; User = daniel.adeniji; ClientProcessId = 5024; NamespaceName = \\.\root\Microsoft\SqlServer\ReportServer
3 GroupOperationId = 159605; OperationId = 159605; Operation = IWbemServices::Connect; ClientMachine = QADB; User = daniel.adeniji; ClientProcessId = 5024; NamespaceName = \\QADB\root\Microsoft\SqlServer\ReportServer\RS_DATACAP\v12\Admin
4 GroupOperationId = 159606; OperationId = 159607; Operation = Start IWbemServices::CreateInstanceEnum – MSReportServer_ConfigurationSetting; ClientMachine = QADB; User = daniel.adeniji; ClientProcessId = 5024; NamespaceName = \\.\root\Microsoft\SqlServer\ReportServer\RS_DATACAP\v12\Admin
5 ProviderInfo for GroupOperationId = 159606; Operation = Provider::CreateInstanceEnum – MSReportServer_ConfigurationSetting; ProviderName = ReportingServicesWMIProvider; ProviderGuid = {0A0B6A3E-DAA2-4ED9-A603-B1C4ED9515FF}; Path = C:\Program Files (x86)\Microsoft SQL Server\120\Shared\reportingserviceswmiprovider.dll



  1. Event #1 :- IWebServices Create Instance Enum
    • NamespaceName :- \\QA\root\Microsoft\SqlServer\ReportServer
  2. Event #2 :- IWebServices Create Instance Enum
    • NamespaceName :- \\.\root\Microsoft\SqlServer\ReportServer
  3. Event #3 :- IWebServices Connect
    • NamespaceName :- \\.\root\Microsoft\SqlServer\ReportServer\RS_DATACAP\v12\Admin
  4. Event #4 :- IWebServices Instance Enumerate
    • NamespaceName :- \\.\root\Microsoft\SqlServer\ReportServer\RS_DATACAP\v12\Admin
  5. Event #5 :- Com Object Instantiated
    • COM Object ID :- 0A0B6A3E-DAA2-4ED9-A603-B1C4ED9515FF
    • COM File :- C:\Program Files (x86)\Microsoft SQL Server\120\Shared\reportingserviceswmiprovider.dll



From logging WMI Calls we are able to see the inner workings of the WMI Provider class and IWbemServices interface.

In the case of Sql Server Reporting Services (SSRS) it is an version specific dll ( C:\Program Files (x86)\Microsoft SQL Server\120\Shared\reportingserviceswmiprovider.dll ).

SSRS – Validating Smart Host – Using Mozilla Thunderbird


A few posts ago, we provisioned a Smart Host.

Let us quickly test it out.



Here are other posts in this multi-series:

  1. SSRS – Setting up Smart Host


To make sure that we understand the specificity of Microsoft’s Office 365 SMTP service, we will install a free, durable email client; specifically Mozilla Thunderbird.




  1. tcp.port == 25 || tcp.port == 465 || tcp.port == 587

Mozilla Thunderbird


Download Mozilla Thunderbird from here.


Installation is straightforward.



Session – 1

SMTP Server Settings





Session – 2

SMTP Server Settings



WireShark – SMTP ( Destination Port 587 ) – 01
WireShark – Explanation
  1. Connection to SMTP Host
WireShark – SMTP ( Destination Port 587 ) – 02

WireShark – Explanation
  1. Reply from SMTP Host


Session – 3

SMTP Server Settings


WireShark – Explanation
  1. We see a fuller conversation


Item Port :- 465 /
Connection :- SSL/TLS
Port :- 587 /
Connection Start :- SSL/TLS
Port :- 587 /
Connection Start :- STARTSSL
Server Name smtp.office365.com smtp.office365.com smtp.office365.com
Port 465 587 587
Connection Security SSL/TLS SSL/TLS STARTTLS
Authentication Password Normal Password Normal Password Normal Password
Results SYN/SENT  Truncated Conversation  Full Conversation


Network Ports

  1. Port :- 25
    • SMTP
      • Server to Server email
        • Message relay port
      • (-)
        • Not Authenticated
        • Blocked by a lot of firewall
  2. Port :- 465
    • SMTP
      • (-)
        • Not widely adopted
  3. Port 587
    • SMTP
      • Mail Submission Port
      •  (+)
        • Authenticated emails



  1. Microsoft
    • Office
      • Support
        • POP and IMAP settings for Outlook Office 365 for business
        • How to set up a multifunction device or application to send email using Office 365
    • technet
      • blogs.technet.com
        • Andrew Stobart – Useful Wireshark Filters for Mail Flow Troubleshooting
  2. Mozilla.Org
    • Mozilla Support
      • cannot send mail. Connected to smtp.office365.com but times out.
  3. Stanford University
    • Stanford | University IT
      • How to Configure Thunderbird for Office 365 Using IMAP
  4. StackOverflow
    • Network Ports
      • What is the difference between ports 465 and 587?
    • Managed File Transfer and Network Solutions
      • John Carl Villanueva
        • Still Confused With SMTP Ports? Read This
  6. FastMail
    • SSL vs TLS vs STARTTLS


SQL Server – Error – “The CREATE UNIQUE INDEX statement terminated because a duplicate key was found for the object name ‘dbo.sysowners’ and the index name ‘nc1’. The duplicate key value”



Trying to add Reporting Services to an existing SQL Server v2014 Install this afternoon, and finally ran into a problem that is worthy of talking about.



We are on MS SQL Server 2014 Standard Edition

  1. Added Reporting Services to an existing install
  2. And, now going through the Change Database Steps
    • Specifically, the Progress and Finish Step
    • While processing the SQL Code within the “Running database script” step, we ran into an Error






Here is the error message

Error Image


Error Text


System.Data.SqlClient.SqlException: The CREATE UNIQUE INDEX statement terminated because a duplicate key was found for the object name 'dbo.sysowners' and the index name 'nc1'. The duplicate key value is (spotlight).
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
   at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at Microsoft.ReportingServices.Common.DBUtils.ApplyScript(SqlConnection conn, String script, ICommandWrapperFactory commandWrapper)
   at Microsoft.ReportingServices.Common.DBUtils.ApplyScript(String connectionString, String script)
   at ReportServicesConfigUI.SqlClientTools.SqlTools.ApplyScript(String connectionString, String script)



SQL Server Profiler

Ran SQL Server Profiler and captured the error pasted below:






The create unique Index Statement terminated because a duplicate key was found for the object ‘dbo.sysowners’ and the index named ‘nc1’.  
The duplicate key value is (spotlight).



Knowing that msdb is the foundational database took a look at it.



use [msdb]

select *

from   sysusers tblSU

--where  lower(tblSU.[name]) like '%spot%'

order by 






  1. In the msdb database
    • We have two distinct users Spotlight and spotlight
    • This is possible as out server collation


Validate Server Collation


print 'Collation: ' + cast( serverproperty('collation') as varchar(60))




Validate Database ( msdb ) Collation


print 'Collation - SQL Instance: ' + cast( serverproperty('collation') as varchar(60))

print 'Collation - Database - msdb - ' + CONVERT (varchar, DATABASEPROPERTYEX('msdb','collation'));  

print 'Collation - Database - ReportServer - ' + CONVERT (varchar, DATABASEPROPERTYEX('ReportServer','collation'));  

print 'Collation - Database - ReportServerTempdb - ' + CONVERT (varchar, DATABASEPROPERTYEX('ReportServerTempDB','collation'));  





  1. On our embryonic database, msdb, it is OK to have users whose name only vary based on case
    • BTW, for this server whose collation is binary, case materializes
  2. But, on new to become database which is case-insensitive, it is not OK




To me it is a cute problem, but don’t ask my lover

As, she is the only one who makes herself pretty for me

Bellamy Brothers
Let Your Love Flow

Microsoft Connect

Opened up a Connect Item

  1. Title :- Reporting Services – Configuration – Index Creation error on table dbo.sysowners – The index name nc1
    ID :- 3120021
    Date Created :- 2107-Jan-30th
    Status :- Active